# Field type (Mapping) conflicts

**URL:** https://discuss.elastic.co/t/field-type-mapping-conflicts/311967
**Category:** Kibana
**Created:** [August 11, 2022, 10:13pm UTC](https://discuss.elastic.co/t/field-type-mapping-conflicts/311967 "2022-08-11T22:13:16Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![ELKcgnuser](https://avatars.discourse-cdn.com/v4/letter/e/3be4f8/32.png) [@ELKcgnuser](https://discuss.elastic.co/u/ELKcgnuser)
#### Post date: [August 11, 2022, 10:13pm UTC](https://discuss.elastic.co/t/field-type-mapping-conflicts/311967/1 "2022-08-11T22:13:16Z")

</div>

I got this error message:

`4 fields are defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data.`

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/b/1b4fba23c3a5c461261b8408326a951be592ace7.png)

The correct field type for each must be:

`message.data` **text**  
`message.ip_address` **ip**  
`message.status_code` **long**  
`message.time` **date**

How can I solve this conflicts?

Thanks for your help in advance

---

<div class="post-metadata">

### Author: ![JLeysens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jleysens/32/67404_2.png) [@JLeysens](https://discuss.elastic.co/u/JLeysens)
#### Post date: [August 12, 2022, 8:53am UTC](https://discuss.elastic.co/t/field-type-mapping-conflicts/311967/2 "2022-08-12T08:53:05Z")

</div>

Hello @ELKcgnuser !

You will need to reindex some set of the indices being targetted by the data view (legacy: index pattern) that you are using. To convert types you could use an ingest pipeline, for example:

> **[Reindex API | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#reindex-with-an-ingest-pipeline)**

See related discuss issue:

> [@Kibana conflict type field](https://discuss.elastic.co/t/kibana-conflict-type-field/270667):
>
> How i can resolve this issues. Kibana field type conflict

---

<div class="post-metadata">

### Author: ![ELKcgnuser](https://avatars.discourse-cdn.com/v4/letter/e/3be4f8/32.png) [@ELKcgnuser](https://discuss.elastic.co/u/ELKcgnuser)
#### Post date: [August 12, 2022, 5:48pm UTC](https://discuss.elastic.co/t/field-type-mapping-conflicts/311967/3 "2022-08-12T17:48:38Z")

</div>

Hi [JLeysens](https://discuss.elastic.co/u/JLeysens)  
Thanks for your help, let me try it this and will back to you with the results. Not totally sure how to do it but will read the documentation and the related discuss issue as well.

---

<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: [September 9, 2022, 5:49pm UTC](https://discuss.elastic.co/t/field-type-mapping-conflicts/311967/4 "2022-09-09T17:49:03Z")

</div>

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