# Upgradation to 0.90.0 giving "No index mapper" Exception on every new field being indexed **URL:** \ **Category:** Elasticsearch\ **Created:** [May 15, 2013, 5:10am UTC](https://discuss.elastic.co/t/upgradation-to-0-90-0-giving-no-index-mapper-exception-on-every-new-field-being-indexed/11966 "2013-05-15T05:10:48Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![NarinderKaur\_Makkar](https://avatars.discourse-cdn.com/v4/letter/n/9de053/32.png) [@NarinderKaur\_Makkar](https://discuss.elastic.co/u/NarinderKaur_Makkar)\ **Post date:** [May 15, 2013, 5:10am UTC](https://discuss.elastic.co/t/upgradation-to-0-90-0-giving-no-index-mapper-exception-on-every-new-field-being-indexed/11966/1 "2013-05-15T05:10:48Z")
``` Hi, I just upgraded my Elasticsearch from 0.20.6 to 0.90.0 for ``` sorting on multivalued fields. Then my nodes health starting gone red when data was indexed to elasticsearch. error log showing an exception: [2013-05-13 08:24:37,404][WARN][cluster.action.shard] [Americop] received shard failed for [es\_15][1], node[vB8PJYecR1W3zCd-Cke2Kg], [P], s[STARTED], reason [engine failure, message [MergeException[org.elasticsearch.ElasticSearchIllegalStateException: no index mapper found for field: [fav\_metadata.fav\_local\_media\_person\_id.count]]; nested: ElasticSearchIllegalStateException[no index mapper found for field: [fav\_metadata.fav\_local\_media\_person\_id.count]]; ]] When i added the missing mapping it started working fine. and then it gave the same error on another field. As far as I know, Elasticsearch adds the dynamic mappings if mappings are not executed. Then this error should not be there. Please help me understand this logic. Because i have so many dynamic created field. And I can not create all of the mappings manually. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [May 15, 2013, 10:28am UTC](https://discuss.elastic.co/t/upgradation-to-0-90-0-giving-no-index-mapper-exception-on-every-new-field-being-indexed/11966/2 "2013-05-15T10:28:31Z")
Hi Narinder Use ignore\_unmapped: curl -XGET '[http://127.0.0.1:9200/\_all/\_search?pretty=1](http://127.0.0.1:9200/_all/_search?pretty=1)' -d ' { "sort" : [ { "my\_field" : { "ignore\_unmapped" : 1, "mode" : "min", "order" : "asc" } } ] } ' On 15 May 2013 07:10, NarinderKaur Makkar [narinderkaurmakkar1@gmail.com](mailto:narinderkaurmakkar1@gmail.com)wrote: > ``` > Hi, > > I just upgraded my Elasticsearch from 0.20.6 to 0.90.0 for > > ``` > > sorting on multivalued fields. Then my nodes health starting gone red when > data was indexed to elasticsearch. error log showing an exception: > > [2013-05-13 08:24:37,404][WARN][cluster.action.shard] [Americop] > received shard failed for [es\_15][1], node[vB8PJYecR1W3zCd-Cke2Kg], [P], > s[STARTED], reason [engine failure, message > [MergeException[org.elasticsearch.ElasticSearchIllegalStateException: no > index mapper found for field: > [fav\_metadata.fav\_local\_media\_person\_id.count]]; nested: > ElasticSearchIllegalStateException[no index mapper found for field: > [fav\_metadata.fav\_local\_media\_person\_id.count]]; ]] > > When i added the missing mapping it started working fine. and then it gave > the same error on another field. As far as I know, Elasticsearch adds the > dynamic mappings if mappings are not executed. Then this error should not > be there. > > Please help me understand this logic. Because i have so many dynamic > created field. And I can not create all of the mappings manually. > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:36am UTC](https://discuss.elastic.co/t/upgradation-to-0-90-0-giving-no-index-mapper-exception-on-every-new-field-being-indexed/11966/3 "2017-07-06T02:36:36Z")