Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *updated* an issue
Hibernate Search (
https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMDRhYjVm...
) / New Feature (
https://hibernate.atlassian.net/browse/HSEARCH-4845?atlOrigin=eyJpIjoiMDR...
) HSEARCH-4845 (
https://hibernate.atlassian.net/browse/HSEARCH-4845?atlOrigin=eyJpIjoiMDR...
) Have a dedicated docvalue field for the root document id in the Lucene backend's
document (
https://hibernate.atlassian.net/browse/HSEARCH-4845?atlOrigin=eyJpIjoiMDR...
)
Change By: Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
)
With a future upgrade to Lucene 9+ comes some additional schema validation on indexing.
This leads to failures when we try to write a nested object, as we don’t add the docvalue
to a root id field. This causes a mismatch between the root and nested object id schema.
To prevent this from happening, we could write a doc value for the nested object too, or
alternatively (which this ticket is about), we can have an additional a separate docvalues
field to retrieve the id from in a root document.
See
[
https://github.com/hibernate/hibernate-search/pull/3485#discussion_r11773...]
(
https://hibernate.atlassian.net/browse/HSEARCH-4845#add-comment?atlOrigin...
) Add Comment (
https://hibernate.atlassian.net/browse/HSEARCH-4845#add-comment?atlOrigin...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100223- sha1:038ca59 )