Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Document the indexing of containers using @Field + @IndexedEmbedded

Description

It is possible to index a collection, array or map of types using @Field but the documentation is missing examples and a description of this feature.

The tests related to this feature are:

  • IterableBridgeTest

  • ArrayBridgeTest

  • MapBridgeTest

Activity

Yoann RodièreSeptember 26, 2023 at 9:37 AM

Hello,

This issue was reported against Hibernate Search 5.x or earlier, and doesn't seem to be relevant to newer Hibernate Search versions (6.x+).

In order to focus on newer versions, we are going to close this issue.

If you are still affected by this issue on Hibernate Search 6.0 or later, and have a reproducer, please comment here or reach out to us so we can reopen the issue.

If you are still affected by this issue on Hibernate Search 5.x, and want to provide a fix, please comment here or reach out to us so we can work out the next steps with you.

Cheers,
Yoann

Yoann RodièreSeptember 18, 2018 at 2:15 PM

No longer relevant in Search 6. Assigning "5.x" as fix version.

Yoann RodièreNovember 14, 2016 at 2:23 PM

I'd be in favor of removing the need for @IndexedEmbedded, and use those field bridges as defaults as soon as there is an @Field annotation on an Iterable/array/map. After all, there's not much sense in indexing those types in any other way. See HSEARCH-2419.
, do you agree? If so, this ticket will only be about documenting the very existence of built-in bridges for iterables/arrays/maps.

Out of Date

Details

Assignee

Reporter

Components

Fix versions

Priority

Created March 28, 2014 at 12:23 PM
Updated September 26, 2023 at 9:37 AM
Resolved September 26, 2023 at 9:37 AM

Flag notifications