Fix standard filter BWC check to allow for cacheing bug #62649
Merged
Conversation
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
romseygeek
added
>bug
:Search Relevance/Analysis
Collaborator
|
Pinging @elastic/es-search (:Search/Analysis) |
jimczi
approved these changes
Sep 18, 2020
Contributor
jimczi
left a comment
jimczi
left a comment
There was a problem hiding this comment.
I left one comment. Thanks for tackling this so quickly!
| preConfiguredTokenFilters.register( "standard", | ||
| PreConfiguredTokenFilter.elasticsearchVersion("standard", true, (reader, version) -> { | ||
| if (version.before(Version.V_7_0_0)) { | ||
| if (version.before(Version.V_7_6_0)) { |
Contributor
There was a problem hiding this comment.
Can you add a comment here so that we don't forget why it's 7.6 and not 7.0 ?
Contributor
Author
|
@elasticmachine update branch |
romseygeek
added a commit
that referenced
this pull request
Sep 21, 2020
The `standard` tokenfilter was removed by #33310, and should have been unuseable in any indexes created since 7.0. However, a cacheing bug fixed by #51092 meant that it was still possible in certain circumstances to create indexes referencing the standard filter in versions up to 7.5.2. Our checks in AnalysisModule still refer to 7.0.0, however, meaning that a cluster that contains one of these rogue indexes cannot be upgraded. This commit adjusts the AnalysisModule checks so that we only refuse to build a mapping referring to standard filter if the index created version is 7.6 or later. Fixes #62644
romseygeek
added a commit
that referenced
this pull request
Sep 21, 2020
The `standard` tokenfilter was removed by #33310, and should have been unuseable in any indexes created since 7.0. However, a cacheing bug fixed by #51092 meant that it was still possible in certain circumstances to create indexes referencing the standard filter in versions up to 7.5.2. Our checks in AnalysisModule still refer to 7.0.0, however, meaning that a cluster that contains one of these rogue indexes cannot be upgraded. This commit adjusts the AnalysisModule checks so that we only refuse to build a mapping referring to standard filter if the index created version is 7.6 or later. Fixes #62644
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
The
standardtokenfilter was removed by #33310, and should have beenunuseable in any indexes created since 7.0. However, a cacheing bug fixed
by #51092 meant that it was still possible in certain circumstances to create
indexes referencing the
standardfilter in versions up to 7.5.2. Our checksin
AnalysisModulestill refer to 7.0.0, however, meaning that a cluster thatcontains one of these rogue indexes cannot be upgraded.
This commit adjusts the AnalysisModule checks so that we only refuse to
build a mapping referring to
standardfilter if the index created version is7.6 or later.
Fixes #62644