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 copy_to feature enabled #110038

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

Support synthetic source for fields with copy_to feature enabled #110038

martijnvg opened this issue Jun 21, 2024 · 1 comment
Assignees
Labels

Comments

@martijnvg
Copy link
Member

Today synthetic source can't be configured if a mapping contains fields with copy_to definitions. The reason why this is disallowed, is that when documents get reindexed we often synthesize from doc values and then the documents in the target index could have accuracy loss. A provided field value at index time value may not be the same at reindex time.

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

@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
Projects
None yet
Development

No branches or pull requests

3 participants