# Mapping Conflicts when re-indexing using a template

**URL:** <https://discuss.elastic.co/t/mapping-conflicts-when-re-indexing-using-a-template/33826>\
**Category:** Elasticsearch\
**Created:** [November 5, 2015, 4:00am UTC](https://discuss.elastic.co/t/mapping-conflicts-when-re-indexing-using-a-template/33826 "2015-11-05T04:00:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tyler\_Field](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Tyler\_Field](https://discuss.elastic.co/u/Tyler_Field)\
**Post date:** [November 5, 2015, 4:00am UTC](https://discuss.elastic.co/t/mapping-conflicts-when-re-indexing-using-a-template/33826/1 "2015-11-05T04:00:22Z")

</div>

I'm attempting to resolve a mapping conflict by first uploading an index template with the mappings for the relevant types explicitly defined and then re-indexing my documents.

However after re-indexing the field is still showing a mapping conflict when viewed in Kibana.

Q1. Could the mapping conflict be caused by the data in the field? i.e. if I am trying to map a field as a geo\_point and it receives string data what does it error?

Q2. Any tips for finding the cause of the mapping conflict? Is there a way to search or see which documents have different mappings for the same field?

---

<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:** [July 5, 2017, 11:40pm UTC](https://discuss.elastic.co/t/mapping-conflicts-when-re-indexing-using-a-template/33826/2 "2017-07-05T23:40:27Z")

</div>