My suggestion is to use two SQL columns "location.lat" and "location.lon" instead of flat "lat" and "lng". With "type": "geo_point" mapping, a geo search should be straightforward.
Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHsZENrafjGR7ejFa8_gehi4WHR3WnqmVqhX5G%2BimPXSg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
