# Type mapping conflict during reindex **URL:** \ **Category:** Elasticsearch\ **Created:** [September 6, 2018, 10:23pm UTC](https://discuss.elastic.co/t/type-mapping-conflict-during-reindex/147638 "2018-09-06T22:23:19Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![MaKro](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@MaKro](https://discuss.elastic.co/u/MaKro)\ **Post date:** [September 6, 2018, 10:23pm UTC](https://discuss.elastic.co/t/type-mapping-conflict-during-reindex/147638/1 "2018-09-06T22:23:19Z")
Hi. I'm trying to automate the process of schema update and after reading the docs I decided to use the approach with aliases and reindex API. Everything was fine when I added for example new analysers or new fields. Things has gone bad when I tried to change a type of an existing field. Here is what I do (I'm skipping some not important details): 1. I have an index with alias attached 2. I create new index 3. I perform reindex from the current index to the new index 4. I switch the alias In the case, where new mappings contain different type for an existing field, I get an error: {"error":{"root\_cause": [{"type":"illegal\_argument\_exception","reason":"mapper [fieldName] of different type, current\_type [keyword], merged\_type ,"type":"illegal\_argument\_exception","reason":"mapper [fieldName] of different type, current\_type [keyword], merged\_type [date]"},"status":400} Is there any way, to ignore such confict, so the reindex API will just skip such conflicted data? Currently it's breaking the process, so I end up with an old index not being updated. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 4, 2018, 10:32pm UTC](https://discuss.elastic.co/t/type-mapping-conflict-during-reindex/147638/2 "2018-10-04T22:32:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.