# Mapping Conflict with several types

**URL:** <https://discuss.elastic.co/t/mapping-conflict-with-several-types/301312>\
**Category:** Kibana\
**Created:** [April 1, 2022, 10:35am UTC](https://discuss.elastic.co/t/mapping-conflict-with-several-types/301312 "2022-04-01T10:35:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![wcpoon](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@wcpoon](https://discuss.elastic.co/u/wcpoon)\
**Post date:** [April 1, 2022, 10:35am UTC](https://discuss.elastic.co/t/mapping-conflict-with-several-types/301312/1 "2022-04-01T10:35:32Z")

</div>

Hi guys,

I'm facing this issues in Data View,

> **Mapping conflict**
> 
> A field is 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.

> syslog\_timestamp -\> date, text (Conflict)

It require reindexing my data.  
But I already deleted the indices which is conflict data inside.  
But the conflict still there.

Any idea how to resolve this?

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [April 11, 2022, 8:41pm UTC](https://discuss.elastic.co/t/mapping-conflict-with-several-types/301312/2 "2022-04-11T20:41:25Z")

</div>

Hello @wcpoon - Which version of the elastic stack are you running?

Could you capture a `har` file which includes the request `fields_for_wildcard`? It will provide useful debugging info.

Thanks,  
Matt

---

<div class="post-metadata">

**Author:** ![wcpoon](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@wcpoon](https://discuss.elastic.co/u/wcpoon)\
**Post date:** [April 12, 2022, 2:43am UTC](https://discuss.elastic.co/t/mapping-conflict-with-several-types/301312/3 "2022-04-12T02:43:42Z")

</div>

Hi @mattkime, I'm running in 8.1.2 now.  
I already resolved the issues. 🙂  
Thanks.

---

<div class="post-metadata">

**Author:** ![matw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matw/32/13913_2.png) [@matw](https://discuss.elastic.co/u/matw)\
**Post date:** [April 12, 2022, 7:00am UTC](https://discuss.elastic.co/t/mapping-conflict-with-several-types/301312/4 "2022-04-12T07:00:48Z")

</div>

@wcpoon mind if you share what solved it? thx!

---

<div class="post-metadata">

**Author:** ![wcpoon](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@wcpoon](https://discuss.elastic.co/u/wcpoon)\
**Post date:** [April 12, 2022, 7:03am UTC](https://discuss.elastic.co/t/mapping-conflict-with-several-types/301312/5 "2022-04-12T07:03:41Z")

</div>

I assigned to another field and different types.

---

<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:** [May 10, 2022, 7:04am UTC](https://discuss.elastic.co/t/mapping-conflict-with-several-types/301312/6 "2022-05-10T07:04:39Z")

</div>

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