Query string query: Remove lowercase_expanded_terms and locale options#10086
Merged
dakrone merged 1 commit intoelastic:masterfrom Mar 13, 2015
Merged
Query string query: Remove lowercase_expanded_terms and locale options#10086dakrone merged 1 commit intoelastic:masterfrom
lowercase_expanded_terms and locale options#10086dakrone merged 1 commit intoelastic:masterfrom
Conversation
Member
|
LGTM |
The analysis chain should be used instead of relying on this, as it is confusing when dealing with different per-field analysers. The `locale` option was only used for `lowercase_expanded_terms`, which, once removed, is no longer needed, so it was removed as well. Fixes elastic#9978 Relates to elastic#9973
This was referenced Apr 6, 2015
lowercase_expanded_terms and locale options
slawo
pushed a commit
to slawo/elastic
that referenced
this pull request
Apr 16, 2018
remove: - lowercase_expanded_terms - locale as per: elastic/elasticsearch#10086
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
3 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 analysis chain should be used instead of relying on this, as it is
confusing when dealing with different per-field analysers.
The
localeoption was only used forlowercase_expanded_terms, which,once removed, is no longer needed, so it was removed as well.
Fixes #9978
Relates to #9973