Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geo: All geo components that accept an array of [lat, lon] to change to do [lon, lat] to conform with GeoJSON #661

Closed
kimchy opened this issue Jan 31, 2011 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Jan 31, 2011

All geo components: geo_point type, all the geo related filters and facets, and sort that accept an array in [lat, lon], changed to [lon, lat] to conform to GeoJSON.

@kimchy
Copy link
Member Author

kimchy commented Jan 31, 2011

Geo: All geo components that accept an array of [lat, lon] to change to do [lon, lat] to conform with GeoJSON, closed by 5da14a7.

mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…pull request elastic#661)

MPC-4721 - Monitoring/alerting on AWS MediaConvert

* add a dedicated queue for every stack

Approved-by: fabien
Approved-by: Can Yildiz
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
As discussed in [^1] this commit removes the indexing chart from
the geoshape nightlies because we aren't interested in indexing
results and they show volatility due to indexing with >1 clients.

[^1]: elastic/elasticsearch-benchmarks#879 (comment)
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant