New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove _analyzer
field
#9381
Remove _analyzer
field
#9381
Conversation
@imotov I updated this to only include _analyzer removal. |
if (!forcedQuoteAnalyzer) { | ||
setAnalyzer(fieldMappers.searchQuoteAnalyzer()); | ||
} | ||
setAnalyzer(fieldMappers.searchQuoteAnalyzer()); | ||
} else { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't these changes belong to query analyzer PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, missed this part when reverting. Will fix.
I left a couple of minor comments, but in general it looks good to me. I also think we should delete analyzer-field.asciidoc from master as part of this PR. |
Thanks @imotov. I pushed fixes for your comments. |
LGTM |
Note that the per query analyzer still exists for MultiTermQuery. That
needs to be looked at separately on how to remove...
closes #9279