Use nested objects mapping and parent-child relationship mapping
Description
is followed up by
relates to
required for
Activity
Show:
Yoann Rodière April 25, 2018 at 8:38 AMEdited
Mostly resolved as part of the Search 6 proof of concept groundwork.
See IndexedEmbedded#storage and SearchPredicateContainerContext#nested in particular.
Followed up by HSEARCH-2254, HSEARCH-3062, HSEARCH-3090, HSEARCH-3065.
Emmanuel Bernard October 31, 2016 at 10:48 AM
Elasticsearch has two interesting features mapping wise
nested objects https://www.elastic.co/guide/en/elasticsearch/guide/current/nested-objects.html
parent child https://www.elastic.co/guide/en/elasticsearch/guide/current/parent-child.html
We should offer the option for a user to chose when an @IndexedEmbedded is mapped as manual denormalization, nested object or parent child.
We can orthogonally add support for this in the Lucene backend.
Fixed
Details
Details
Assignee
Yoann RodièreReporter
Guillaume SmetComponents
Fix versions
Priority
MajorCreated April 29, 2016 at 10:29 AM
Updated November 28, 2018 at 3:43 PM
Resolved April 25, 2018 at 8:38 AM
Enable nested mapping as needed:
only needed for embedded *-to-many with more than one field
for these, the user should be able to opt out (nested would be the safe default mapping in this case, but they could want to opt out when only ever querying on single fields of the embeddable)
It might be a logic we could also use for the Lucene backend and if we came up with such a complicated scheme to determine if a field is going to be nested or not, we will probably need to integrate these information in the metada.