@IndexedEmbedded.includePaths should allow to pick paths that were excluded from the embedded entity
Description
Activity
Show:
Yoann Rodière November 3, 2020 at 7:55 AMEdited
https://hibernate.atlassian.net/browse/HSEARCH-3903#icft=HSEARCH-3903 may provide an alternative solution to this problem.
Yoann Rodière June 12, 2018 at 2:22 PMEdited
I think we could make this work in 6, but this conflicts quite directly with https://hibernate.atlassian.net/browse/HSEARCH-2552, which states exactly the opposite. Adding this to the next milestone so that we can have a look.
Marc Schipperheyn June 19, 2015 at 12:53 PM
Perhaps one to consider for 5.4?
Marc Schipperheyn June 3, 2015 at 1:24 PM
Bump
Marc Schipperheyn August 8, 2013 at 1:58 PM
I would recommend adding a fix/version for this one, preferable: next. This is too fundamental to leave lying around
Details
Details
Assignee
Unassigned
UnassignedReporter
Marc SchipperheynComponents
Fix versions
Priority
Major
Created April 28, 2012 at 9:05 PM
Updated September 25, 2023 at 3:53 PM
Currently includePaths can only be used in a root entity A.
If you use includePaths also in the embedded entity that is a root entity itself, any paths from A to C will fail, because using includePaths in the embedded entity B will set depth to 0.
In most cases, this is ok, however, it can be very limiting and this limitation shouldn't be there.
@Indexed public class A{ @IndexedEmbedded(includePaths={"id","c.date"} public B getB(){ return b; } } @Indexed public class B{ @IndexedEmbedded(includePaths={"label"} public C getC(){ return c; } }The above code will lead c.date to not be indexed because of includePaths="label".