Use stored fallback fields when time series doc values format is not used#140471
Merged
Kubik42 merged 1 commit intoelastic:mainfrom Jan 13, 2026
Merged
Conversation
3a0409e to
0e2bf57
Compare
0e2bf57 to
9894a9d
Compare
Collaborator
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
eranweiss-elastic
pushed a commit
to eranweiss-elastic/elasticsearch
that referenced
this pull request
Jan 15, 2026
spinscale
pushed a commit
to spinscale/elasticsearch
that referenced
this pull request
Jan 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We only want to use fallback binary doc values when time series format is enabled, otherwise storing values in a
StoredFieldis more efficient.This PR reintroduces using
StoredFieldsfor fallback text fields based on the value ofuseBinaryDocValues.