When dealing with large entities with many indexed fields, we would like to use {{@IndexedEmbedded.includePath}} feature, as opposed to {{@IndexedEmbedded.depth}}, so that the set of embedded entities that trigger a full reindexing of the parent entity (because of a {{@ContainedIn}}) is minimal.
Unfortunately, it seems that when an entity is changed, Hibernate Search jumps from entity to entity based on the {{@ContainedIn}} annotations and on the {{@IndexedEmbbedded.depth}} feature. So, if {{@IndexedEmbedded.depth}} keeps its default value (which often is the case when using {{includePaths}}) it will ultimately jump to unnecessary entities.
This description probably isn't very clear, so I'll attach a test case. I just need the jira key.
Important note: this bug also affects branch {{4.5}}, which would greatly benefit from backporting the eventual fix.
This description probably isn't very clear, so I'll attach a test case. I just need the jira key.
Might be related: HSEARCH-638
Possible duplicate (not sure, since it's not the same version): HSEARCH-1701 |
|