Change the recommended tie-breaking fields from [_id] to [_seq_no, _shard].
#25797
Conversation
This file contains 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
…, `_shard`]. `_id` requires fielddata to be loaded into memory for sorting, which does not scale on large clusters. Adding doc values to the `_id` field proved controversial so instead, we are removing use-cases for fieddata on the `_uid` or `_id` fields. Relates elastic#25240
jpountz
added
:Search Foundations/Mapping
|
Discussed in FixitFriday: we'd rather implement #25674 and tie break on |
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.
_idrequires fielddata to be loaded into memory for sorting, which does notscale on large clusters. Adding doc values to the
_idfield provedcontroversial so instead, we are removing use-cases for fieddata on the
_uidor
_idfields.Relates #25240