I got new mapping conflict warning message. I don't know why...
Some of your indexes have geoip.location as a geo_point and some have them as double.
and still I have same situation.
Kibana still complains about there not being any geo_point fields even though everything indicates that geoip.location is a geo_point? Okay, I give up. Ask about this in the Kibana category. Just double-check with the get mapping API that geoip.location really is a geo_point for the most recent index.