" Part of the problem lies in the fact we may not know what fields a class bridge will add to the document, and (worse) we can't tell the bridge to add some fields, but ignore some other fields.
We \r\n\r\nWe can fix it either :\r\n\r\n* by overhauling completely how {{@IndexedEmbedded.includePaths}} works ( , i.e. do actual field filtering instead of bridge filtering . This would require breaking APis , which is what in all likeliness, and we do already fixed this in the Search 6 proof of concept ), .\r\n* or by changing the documentation to mention that we only guarantee that we will include those fields, and will try to exclude unnecessary fields on a best-effort basis. Currently we state that we include the given fields and only those fields, which is wrong.
Note \r\n\r\nNote that even if it's already fixed in the Search 6 proof of concept, we should still add tests there .
See \r\n\r\nSee https://discourse.hibernate.org/t/restricting-indexing-of-embedded-entity-fields/943 " |
|
