# Mapper for \[name\] conflicts with existing mapping in other types

**URL:** <https://discuss.elastic.co/t/mapper-for-name-conflicts-with-existing-mapping-in-other-types/94474>\
**Category:** Elasticsearch\
**Created:** [July 25, 2017, 12:37pm UTC](https://discuss.elastic.co/t/mapper-for-name-conflicts-with-existing-mapping-in-other-types/94474 "2017-07-25T12:37:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yapeng\_lee](https://avatars.discourse-cdn.com/v4/letter/y/9fc29f/32.png) [@yapeng\_lee](https://discuss.elastic.co/u/yapeng_lee)\
**Post date:** [July 25, 2017, 12:37pm UTC](https://discuss.elastic.co/t/mapper-for-name-conflicts-with-existing-mapping-in-other-types/94474/1 "2017-07-25T12:37:56Z")

</div>

HI,  
when I use PutMapping , I got some error messages  
**Mapper for [name] conflicts with existing mapping in other types : \*\*  
\*\* [mapper [name] has different [store] values,mapper [name] has different [analyzer]]**

I use update\_all\_types ,but it does not work,what can I do

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 25, 2017, 1:45pm UTC](https://discuss.elastic.co/t/mapper-for-name-conflicts-with-existing-mapping-in-other-types/94474/2 "2017-07-25T13:45:48Z")

</div>

Describe exactly what you are doing but a good way to get rid of that message is to use only one single type per index.

---

<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:** [August 22, 2017, 1:45pm UTC](https://discuss.elastic.co/t/mapper-for-name-conflicts-with-existing-mapping-in-other-types/94474/3 "2017-08-22T13:45:49Z")

</div>

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