# Random non-analyzed mappings in ElasticSearch **URL:** \ **Category:** Elasticsearch\ **Created:** [September 13, 2016, 9:24pm UTC](https://discuss.elastic.co/t/random-non-analyzed-mappings-in-elasticsearch/60428 "2016-09-13T21:24:53Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![grokos](https://avatars.discourse-cdn.com/v4/letter/g/858c86/32.png) [@grokos](https://discuss.elastic.co/u/grokos)\ **Post date:** [September 13, 2016, 9:24pm UTC](https://discuss.elastic.co/t/random-non-analyzed-mappings-in-elasticsearch/60428/1 "2016-09-13T21:24:53Z")
Hi. Recently I have faced a strange problem and trying to figure out the root cause of that. Logstash was creating indices in ES where all string fields were not analyzed(all other days we have it all analyzed always and we use raw fields in Kibana). So at some point Kibana was not finding a data since raw fields were missing, Next day it went back to normal and all string fields are analyzed again, My question is, what could cause ES to stop analyzing fields in documents coming from Logstash? I would like to prevent this from happening. Thank you ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:20pm UTC](https://discuss.elastic.co/t/random-non-analyzed-mappings-in-elasticsearch/60428/2 "2017-07-05T22:20:29Z")