# Mapping conflict resolution

**URL:** <https://discuss.elastic.co/t/mapping-conflict-resolution/76756>\
**Category:** Elasticsearch\
**Created:** [February 28, 2017, 10:09am UTC](https://discuss.elastic.co/t/mapping-conflict-resolution/76756 "2017-02-28T10:09:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sagar\_Birla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sagar_birla/32/15793_2.png) [@Sagar\_Birla](https://discuss.elastic.co/u/Sagar_Birla)\
**Post date:** [February 28, 2017, 10:09am UTC](https://discuss.elastic.co/t/mapping-conflict-resolution/76756/1 "2017-02-28T10:09:03Z")

</div>

I am planning to upgrade my ES cluster from 1.x to 2.x  
Earlier, I had 2 types in a single index which had the mapping conflict.  
So, I planned to break the two indices into separate indices, which resolved the mapping conflict issue.

And, then I had setup an alias which points to both the indices.  
Now, the problem is aliases allow only \_search APIs. So, I am kind of stuck right now.  
If I can not use the alias name, then that would mean lot of changes in app code.

Thankfully, I have done all this on y staging cluster and not production.  
What is the best way to go around?

---

<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:** [March 28, 2017, 10:09am UTC](https://discuss.elastic.co/t/mapping-conflict-resolution/76756/2 "2017-03-28T10:09:12Z")

</div>

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