# IP address mapping conflict
**URL:** https://discuss.elastic.co/t/ip-address-mapping-conflict/76436
**Category:** Kibana
**Created:** [February 24, 2017, 6:31pm UTC](https://discuss.elastic.co/t/ip-address-mapping-conflict/76436 "2017-02-24T18:31:21Z")
**Posts on this page:** 1
**Showing post:** 2
### Author:  [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)
#### Post date: [February 24, 2017, 10:01pm UTC](https://discuss.elastic.co/t/ip-address-mapping-conflict/76436/2 "2017-02-24T22:01:40Z")
Hi Marky, from a quick Google search for "kibana field conflict", I found these links which sound like the same thing you're describing:
> [@Mapping conflict!](https://discuss.elastic.co/t/mapping-conflict/40248):
>
> Dear community, I have a mapping conflicts in across our indices (separated on a daily basis): 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 re-indexing your data. Yesterday I changed via logstash % {NUMBER: bytes: int} a f…
> [@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…
>
>
> Mapping conflict! 14 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.
>
> Use the following command to create an index.
> \#
>
> curl -XPUT localhost:9200/\_river/my\_csv\_river/\_meta -d'
> {
> "type" : "csv",
> "csv\_file" : {
> "folder" : "/home/paqs/Downloads/kibana/hun",
> "filename\_pattern" : ".\*\\.csv$",
> "poll":"1m",
> "fields" : \[
> "SiNo",
> "UserId",
> "UserName",
> "Time",
> "Latitude",
> "Longitude",
> "Sublocation",
> "Location",
> "State",
> "Country",
> "Temperature",
> "Prefferedtemp",
> "AvgPtemp",
> "Humidity",
> "AvgHum",
> "Pollution",
> "AvgPollution",
> "Dust",
> "Davg"
> \],
> "first\_line\_is\_header" : "false",
> "field\_separator" : ",",
> "escape\_character" : "\\",
> "quote\_character" : "\\"",
> "field\_id" : "id",
> "field\_timestamp" : "imported\_at",
> "concurrent\_requests" : "1",
> "charset" : "UTF-8",
> "script\_before\_file": "/home/paqs/Downloads/kibana/hun/before\_file.sh",
> "script\_after\_file": "/home/paqs/Downloads/kibana/hun/after\_file.sh",
> "script\_before\_all": "/home/paqs/Downloads/kibana/hun/before\_all.sh",
> "script\_after\_all": "/home/paqs/Downloads/kibana/hun/after\_all.sh"
> },
> "index" : {
> "index" : "han",
> "type" : "chal",
> "bulk\_size" : 1000,
> "bulk\_threshold" : 10
> }
> }'
>
> curl -XPUT http://localhost:9200/han -d '
> {
> "settings" : {
> "number\_of\_shards" : 1
> },
> "mappings" : {
> "alert" : {
> "properties" : {
> "UserName" : {"type" : "string", "index" : "not\_analyzed"},
> "Sublocation" : {"type" : "string", "index" : "not\_analyzed"},
> "Location" : {"type" : "string", "index" : "not\_analyzed"},
> "State" : {"type" : "string", "index" : "not\_analyzed"},
> "Country" : {"type" : "string", "index" : "not\_analyzed"},
> "Time" : {"type" : "date", "ignore\_malformed" : true, "format" : "dateOptionalTime"},
> "Pollution" : {"type" : "integer"},
> "Dust" : {"type" : "integer"},
> "UserId" : {"type" : "integer"},
> "SiNo" : {"type" : "long"},
> "Humidity" : {"type" : "double"},
> "Prefferedtemp" : {"type" : "double"},
> "Temperature" : {"type" : "double"},
> "AvgHum" : {"type" : "double"},
> "AvgPtemp" : {"type" : "double"},
> "AvgPollution" : {"type" : "double"},
> "Davg" : {"type" : "double"},
> "Latitude" : {"type" : "double"},
> "Longitude" : {"type" : "double"}
> }
> }
> }
> }'
>
> 5)
> This is my csv file contains these value
> example row\[1\]:-------"342379","875","Testaasim","1412294400","12.9289196","77.6352281"," Koramangala","Bengaluru","Karnataka","India","33.6","23","23.177777777778","54.6","54.722222222222","858","847","0","824.88888888889"
> Row\[2\]:------ "350214","875","Testaasim","1412294400","12.928922","77.6352343"," Koramangala "," Bengaluru","Karnataka"," India","33.3","23","23.177777777778","54.5","54.722222222222","580","847","6681","824.88888888889"
>
> y the confilt error is occuring did i need to change any thing in index or mapping ..plzz some one resolve this confilt ....
>
[https://dev.sobeslavsky.net/kibana-how-to-solve-mapping-conflict/](https://dev.sobeslavsky.net/kibana-how-to-solve-mapping-conflict/)
The common answer to this problem is to reindex your data. Please try that and let me know if it helps!
Thanks,
CJ
---
_[View the full topic](https://discuss.elastic.co/t/ip-address-mapping-conflict/76436)._