Remove too_many_fields upgrade check#82809
Merged
romseygeek merged 2 commits intoelastic:7.17from Jan 20, 2022
Merged
Conversation
Collaborator
|
Pinging @elastic/es-search (Team:Search) |
jpountz
approved these changes
Jan 19, 2022
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
4 participants
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.
This check issues a warning if the cluster contains an index that has more
than 1024 fields, and no
default_fieldset for searching. However, the 1024boolean clause limit is no longer relevant with #81850, and in any case this
isn't something that would have prevented a successful upgrade from 7.17 to
8.0, so we can remove the check entirely.
Fixes #81539