Mapping conflict! – Kibana – Discuss the Elastic Stack

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!

Read more here: Source link