You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latitude and longitude values are being reversed by the GeoDistanceFilterBuilder when attempted to construct a search. I have had to do the following in my client code:
searchClient.prepareSearch("stores")
.setTypes("store")
.setQuery(QueryBuilders.matchAllQuery())
.setFilter(FilterBuilders.geoDistanceFilter("location")
.lat(longitude) // BUG: These are reversed in the ES API
.lon(latitude)
Fixing this issue would however break the backwards compatibility of the API, if anyone happened to be relying on this functionality being reversed to get their application working.
The text was updated successfully, but these errors were encountered:
Adds initial very minimal support for geo_shapes to SQL. For now, geoshapes are
converted into String instead of Geometry objects on the JDBC side and no effort
to parse the result is performed.
Relates #4080
The latitude and longitude values are being reversed by the GeoDistanceFilterBuilder when attempted to construct a search. I have had to do the following in my client code:
The issue is with the following line of code:
https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/index/query/GeoDistanceFilterBuilder.java#L125
Fixing this issue would however break the backwards compatibility of the API, if anyone happened to be relying on this functionality being reversed to get their application working.
The text was updated successfully, but these errors were encountered: