Kibana: Mapping conflict! 14 fields are defined as several types

[Vinaymuthanna]

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 ....

[rashidkpc]

This is not a bug, the message is informing you that your index pattern matches several indices and one or more fields are mapped as two or more types.

[ajay2881]

but how to fix it ?
I wanted to test Tile Map and for that I have hardcoded the geo location by added below line to my config file-
mutate {
add_field => [ "geoip.location", [9,51]]
}
Also I am not adding mapping manually as defined above.
Now in my Kibana I get mapping conflict for this geoip.location field.
How to fix this please?

[harishmaiya]

+1 Any suggested fixes for above behavior?

[anhlqn]

@harishmaiya you can either delete or close old indices that have different data types. Another way is to turn on ignore conflict on a mapping. More info https://www.elastic.co/guide/en/elasticsearch/reference/1.4/indices-put-mapping.html

[harishmaiya]

Delete or closing old indices is not an option for me..
Will try turning on ignore conflict on mapping.
Thanks @anhlqn !

[anhlqn]

@harishmaiya other way is to re-index data with new mapping.

[mdamir]

In my case, the indices are being populated automatically using fluentd elastic search plugin. Does not kibana have a way to take the mapping from the latest index? I think this could be a really useful feature.