# Mapper for \[kibanaSavedObjectMeta.searchSourceJSON\] conflicts with existing mapping in other types

**URL:** <https://discuss.elastic.co/t/mapper-for-kibanasavedobjectmeta-searchsourcejson-conflicts-with-existing-mapping-in-other-types/113241>\
**Category:** Elasticsearch\
**Created:** [December 26, 2017, 6:27pm UTC](https://discuss.elastic.co/t/mapper-for-kibanasavedobjectmeta-searchsourcejson-conflicts-with-existing-mapping-in-other-types/113241 "2017-12-26T18:27:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![asidoren](https://avatars.discourse-cdn.com/v4/letter/a/b5ac83/32.png) [@asidoren](https://discuss.elastic.co/u/asidoren)\
**Post date:** [December 26, 2017, 6:27pm UTC](https://discuss.elastic.co/t/mapper-for-kibanasavedobjectmeta-searchsourcejson-conflicts-with-existing-mapping-in-other-types/113241/1 "2017-12-26T18:27:54Z")

</div>

After update from Elasticsearch 2.1 to 5.6 got this error in Elasticsearch log:

> java.lang.IllegalArgumentException: Mapper for [kibanaSavedObjectMeta.searchSourceJSON] conflicts with existing mapping in other types:  
> [mapper [kibanaSavedObjectMeta.searchSourceJSON] is used by multiple types. Set update\_all\_types to true to update [fielddata] across all types.]  
> at org.elasticsearch.index.mapper.FieldTypeLookup.checkCompatibility(FieldTypeLookup.java:130) ~[elasticsearch-5.6.0.jar:5.6.0]

Did it generate a bad mapping during upgrade?

---

<div class="post-metadata">

**Author:** ![luiz.santos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luiz.santos/32/24664_2.png) [@luiz.santos](https://discuss.elastic.co/u/luiz.santos)\
**Post date:** [December 28, 2017, 12:47pm UTC](https://discuss.elastic.co/t/mapper-for-kibanasavedobjectmeta-searchsourcejson-conflicts-with-existing-mapping-in-other-types/113241/2 "2017-12-28T12:47:14Z")

</div>

Hi @asidoren,

In Elasticsearch 5.X fields in the same index with the same name in two different types must have the same mapping, as they are backed by the same field internally.

[https://www.elastic.co/guide/en/elasticsearch/reference/5.0/indices-put-mapping.html#merging-conflicts](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/indices-put-mapping.html#merging-conflicts)

You should fix this.

Cheers,  
LG

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 25, 2018, 12:47pm UTC](https://discuss.elastic.co/t/mapper-for-kibanasavedobjectmeta-searchsourcejson-conflicts-with-existing-mapping-in-other-types/113241/3 "2018-01-25T12:47:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.