Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support synthetic source for fields with normalizers enabled #110039

Open
martijnvg opened this issue Jun 21, 2024 · 1 comment
Open

Support synthetic source for fields with normalizers enabled #110039

martijnvg opened this issue Jun 21, 2024 · 1 comment
Assignees
Labels
>enhancement :StorageEngine/Logs You know, for Logs :StorageEngine/Mapping The storage related side of mappings Team:StorageEngine

Comments

@martijnvg
Copy link
Member

Today synthetic source can't be configured if a mapping contains keyword fields with normalizers. The reason why this is disallowed, is that when documents get reindexed we can't synthesize from doc values because the original value was altered.

In order to support synthetic source when normalizers are enabled, we should enforce storing these fields, so that we can synthesize from stored fields and avoid the potential accuracy loss at reindex time.

@martijnvg martijnvg added >enhancement :StorageEngine/Mapping The storage related side of mappings labels Jun 21, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-storage-engine (Team:StorageEngine)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :StorageEngine/Logs You know, for Logs :StorageEngine/Mapping The storage related side of mappings Team:StorageEngine
Projects
None yet
Development

No branches or pull requests

3 participants