Proper normalization of text and keyword fields#6734
Merged
Bargs merged 1 commit intoelastic:masterfrom Apr 1, 2016
Merged
Conversation
Contributor
|
LGTM |
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
2 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.
Fixes #6722
Related to #6411
ES added
keywordandtextfield types to replacestringin 5.0. Kibana should normalize both of these tostringjust like it normalizes numeric types tonumber, but it needs to marktextfields as analyzed.More info on the ES changes here: https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking_50_mapping_changes.html#breaking_50_mapping_changes