# Mapping conflict! **URL:** \ **Category:** Kibana\ **Created:** [November 24, 2021, 2:49pm UTC](https://discuss.elastic.co/t/mapping-conflict/290084 "2021-11-24T14:49:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Skeldren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skeldren/32/100025_2.png) [@Skeldren](https://discuss.elastic.co/u/Skeldren)\ **Post date:** [November 24, 2021, 2:49pm UTC](https://discuss.elastic.co/t/mapping-conflict/290084/1 "2021-11-24T14:49:16Z")
Hey Guys! I have a question regarding a problem of Mapping conflict! I had to change one field type from string to integer. Due to the Index pattern include include both old indexes and new indexes, there are now conflicts in this field in kibana. From what im seeing one way to fix is to reindex the older indexes into new ones with the new type. But i wanted to avoid this. Is there a possibility to set like a default or priority field type in kibana that would fix this problem? Thanks in advance! ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 24, 2021, 11:30pm UTC](https://discuss.elastic.co/t/mapping-conflict/290084/2 "2021-11-24T23:30:04Z")
(We aren't all guys 😉 ) > [@Skeldren](#): > > Is there a possibility to set like a default or priority field type in kibana that would fix this problem? Nope. Why do yo want to avoid a reindex? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 22, 2021, 11:30pm UTC](https://discuss.elastic.co/t/mapping-conflict/290084/3 "2021-12-22T23:30:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.