# Kibana conflict type field

**URL:** https://discuss.elastic.co/t/kibana-conflict-type-field/270667
**Category:** Kibana
**Tags:** ilm-index-lifecycle-management
**Created:** [April 20, 2021, 7:38am UTC](https://discuss.elastic.co/t/kibana-conflict-type-field/270667 "2021-04-20T07:38:51Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Nazakat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nazakat/32/83692_2.png) [@Nazakat](https://discuss.elastic.co/u/Nazakat)
#### Post date: [April 20, 2021, 7:38am UTC](https://discuss.elastic.co/t/kibana-conflict-type-field/270667/1 "2021-04-20T07:38:51Z")

</div>

How i can resolve this issues. Kibana field type conflict

 ![Screenshot (5)](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1f493083f0b18f829d871ad8d0b99402a5cf06e9.png)

---

<div class="post-metadata">

### Author: ![devon.thomson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/devon.thomson/32/85468_2.png) [@devon.thomson](https://discuss.elastic.co/u/devon.thomson)
#### Post date: [April 20, 2021, 4:09pm UTC](https://discuss.elastic.co/t/kibana-conflict-type-field/270667/2 "2021-04-20T16:09:58Z")

</div>

Hi @nazakat,

It looks like you may need to reindex one or more of the indices that make up this index pattern to resolve the conflict. See this previous discuss thread for more information:

> [@How to fix mapping conflict?](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072):
>
> I have a few fields (bytesSent, bytesReceived, timetaken) that show mapping conflicts, and thus I cannot visualize them in Kibana. All of these log entries are going to an index "logstash-\*" I am pretty green at this, so how would I go about finding all of the conflicting indexes and fixing or removing them? Here is part of the grok expression used for these conflicting fields in Logstash: %{NUMBER:bytesSent} %{NUMBER:bytesReceived} %{NUMBER:timetaken} And then a mutate (is this even necess…

---

<div class="post-metadata">

### Author: ![Nazakat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nazakat/32/83692_2.png) [@Nazakat](https://discuss.elastic.co/u/Nazakat)
#### Post date: [April 21, 2021, 4:53am UTC](https://discuss.elastic.co/t/kibana-conflict-type-field/270667/3 "2021-04-21T04:53:42Z")

</div>

> [@devon.thomson](#):
>
> previous d

Thank to reply. How can i reindexing in kibana

---

<div class="post-metadata">

### Author: ![devon.thomson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/devon.thomson/32/85468_2.png) [@devon.thomson](https://discuss.elastic.co/u/devon.thomson)
#### Post date: [April 21, 2021, 2:22pm UTC](https://discuss.elastic.co/t/kibana-conflict-type-field/270667/4 "2021-04-21T14:22:52Z")

</div>

You can find a guide for reindexing in the docs

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

This should be pretty comprehensive, and you can apply any of the queries it mentions via the Kibana Dev tools.

Additionally, this article contains a guide to reindexing using logstash which has been helpful in the past.

> **[Recipe: Reindexing Elasticsearch Documents with Logstash - Sematext](https://sematext.com/blog/recipe-reindexing-elasticsearch-documents-with-logstash/)**
>
> If you’re working with Elasticsearch, it’s very likely that you’ll need to reindex data at some point. The most popular reason is that you need a mapping change that is incompatible with your current mapping. New fields can be added \[…\]

Good luck!

---

<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 19, 2021, 2:23pm UTC](https://discuss.elastic.co/t/kibana-conflict-type-field/270667/5 "2021-05-19T14:23:22Z")

</div>

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