# How to fix mapping conflict?
**URL:** https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072
**Category:** Kibana
**Created:** [July 8, 2016, 5:14pm UTC](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072 "2016-07-08T17:14:58Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@filebeat\_win](https://discuss.elastic.co/u/filebeat_win)
#### Post date: [July 8, 2016, 5:14pm UTC](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072/1 "2016-07-08T17:14:58Z")
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 necessary?)
```
mutate {
convert => ["bytesSent", "integer"]
convert => ["bytesReceived", "integer"]
convert => ["timetaken", "integer"]
}
```
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 8, 2016, 8:54pm UTC](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072/2 "2016-07-08T20:54:57Z")
You need to reindex the data so that it's all the same.
---
### Author:  [@filebeat\_win](https://discuss.elastic.co/u/filebeat_win)
#### Post date: [July 8, 2016, 9:06pm UTC](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072/3 "2016-07-08T21:06:28Z")
and how can this be accomplished if it is all under logstash-\*?
again, I am very unfamiliar with the process... I tried reading the article from [Elastic.co](http://Elastic.co) but was lost. Is it something I would have to do through Putty or another tool?
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [July 9, 2016, 4:38pm UTC](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072/4 "2016-07-09T16:38:38Z")
> and how can this be accomplished if it is all under logstash-\*?
The principle is that you copy each document in each index into one or more new index. When you're done, delete the old indexes.
> again, I am very unfamiliar with the process... I tried reading the article from [Elastic.co](http://Elastic.co) but was lost. Is it something I would have to do through Putty or another tool?
Reindexing can be done from any language with an Elasticsearch client library. Well, strictly speaking it can be done in any language where it's reasonably convenient to perform HTTP requests.
If you can ask more specific questions it'll be easier to help.
---
### Author:  [@anhlqn](https://discuss.elastic.co/u/anhlqn)
#### Post date: [July 10, 2016, 1:08am UTC](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072/5 "2016-07-10T01:08:18Z")
These two should give you some hints
[http://david.pilato.fr/blog/2015/05/20/reindex-elasticsearch-with-logstash/](http://david.pilato.fr/blog/2015/05/20/reindex-elasticsearch-with-logstash/)
> **[Recipe: Reindexing Elasticsearch Documents with Logstash](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 because you need a mapping change that is incompatible with your…
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072/6 "2017-07-06T13:47:28Z")