Changing the default analyzer in ElasticSearch or LogStash
问题 I've got data coming in from Logstash that's being analyzed in an overeager manner. Essentially, the field "OS X 10.8" would be broken into "OS" , "X" , and "10.8" . I know I could just change the mapping and re-index for existing data, but how would I change the default analyzer (either in ElasticSearch or LogStash) to avoid this problem in future data? Concrete Solution: I created a mapping for the type before I sent data to the new cluster for the first time. Solution from IRC: Create an