Yes, I've tried reloading the index in Kibana. I've also removed the setting and re-added it, but in both cases the geoip fields weren't mapped to geo_point
.
Running curl 'localhost:9200/logstash-nginx-access-2015.11.19/_mapping?pretty=true
outputs the following. You can see that the geoip.location
field is given a double
type, as in the GitHub issue.
{
"logstash-nginx-access-2015.11.19" : {
"mappings" : {
"nginx_access" : {
"properties" : {
"@timestamp" : {
"type" : "date",
"format" : "strict_date_optional_time||epoch_millis"
},
"@version" : {
"type" : "string"
},
"agent" : {
"type" : "string"
},
"auth" : {
"type" : "string"
},
"bytes" : {
"type" : "string"
},
"clientip" : {
"type" : "string"
},
"count" : {
"type" : "long"
},
"fileinfo" : {
"type" : "object"
},
"geoip" : {
"properties" : {
"area_code" : {
"type" : "long"
},
"city_name" : {
"type" : "string"
},
"continent_code" : {
"type" : "string"
},
"country_code2" : {
"type" : "string"
},
"country_code3" : {
"type" : "string"
},
"country_name" : {
"type" : "string"
},
"dma_code" : {
"type" : "long"
},
"ip" : {
"type" : "string"
},
"latitude" : {
"type" : "double"
},
"location" : {
"type" : "double"
},
"longitude" : {
"type" : "double"
},
"real_region_name" : {
"type" : "string"
},
"region_name" : {
"type" : "string"
},
"timezone" : {
"type" : "string"
}
}
},
"httpversion" : {
"type" : "string"
},
"ident" : {
"type" : "string"
},
"input_type" : {
"type" : "string"
},
"line" : {
"type" : "long"
},
"message" : {
"type" : "string"
},
"offset" : {
"type" : "long"
},
"referrer" : {
"type" : "string"
},
"request" : {
"type" : "string"
},
"response" : {
"type" : "string"
},
"shipper" : {
"type" : "string"
},
"source" : {
"type" : "string"
},
"tags" : {
"type" : "string"
},
"timestamp" : {
"type" : "string"
},
"type" : {
"type" : "string"
},
"verb" : {
"type" : "string"
}
}
}
}
}
}