WA-NEW-011: Remove use_dis_max from query_string queries (ES7 compatibility)#634
Open
kitcommerce wants to merge 1 commit intonextfrom
Open
WA-NEW-011: Remove use_dis_max from query_string queries (ES7 compatibility)#634kitcommerce wants to merge 1 commit intonextfrom
kitcommerce wants to merge 1 commit intonextfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Remove the deprecated
use_dis_maxoption fromquery_stringqueries inProductSearchandHelpSearch. This option was removed in Elasticsearch 7 and causes a 400parsing_exception.Closes #628
Client impact
None expected.
use_dis_maxwas already the default behavior in ES5/6; removing it explicitly is a no-op for query semantics. Thetie_breakerparameter (which replaces the dis_max behavior) is retained.Verify