mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-29 01:44:36 -04:00
5f7ea792ac
* Soft-deprecation of point/geo_point formats Since GeoJSON and WKT are now common formats for all three types: geo_shape, geo_point and point We decided to soft-deprecate the other point formats by ordering: * GeoJSON (object with keys `type` and `coordinates`) * WKT `POINT(x y)` * Object with keys `lat` and `lon` (or `x` and `y` for point) * Array [lon,lat] * String `"lat,lon"` (or `"x,y"` in point) * String with geohash (only in `geo_point`) The geohash is last because it is only in one field type. The string version is second last because it is the most controversial being the only version to reverse the coordinate order from all other formats (for geo_point only, since the coordinates are not reversed in point). In addition we replaced many examples in both documentation and tests to prioritize WKT over the plain string format. Many remaining examples of array format or object with keys still exist and could be replaced by, for example, GeoJSON, if we feel the need. * Incorrect quote position |
||
|---|---|---|
| .. | ||
| search-your-data | ||
| suggesters | ||
| async-search.asciidoc | ||
| clear-scroll-api.asciidoc | ||
| count.asciidoc | ||
| explain.asciidoc | ||
| field-caps.asciidoc | ||
| knn-search.asciidoc | ||
| multi-search-template-api.asciidoc | ||
| multi-search.asciidoc | ||
| point-in-time-api.asciidoc | ||
| profile.asciidoc | ||
| rank-eval.asciidoc | ||
| render-search-template-api.asciidoc | ||
| scroll-api.asciidoc | ||
| search-shards.asciidoc | ||
| search-template-api.asciidoc | ||
| search-vector-tile-api.asciidoc | ||
| search.asciidoc | ||
| suggesters.asciidoc | ||
| terms-enum.asciidoc | ||
| validate.asciidoc | ||