honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-22 21:05:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

clarification on geo distance sorting (#21779)

Browse Source 
* clarification on geo distance sorting

* applying the suggested change
This commit is contained in:
Adrin Jalali 2016-11-24 16:05:41 +01:00 committed by Clinton Gormley
parent 41e9ed13d6
commit 0871073f9b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/search/request/sort.asciidoc
View File

@ -213,7 +213,7 @@ then Elasticsearch will handle it as if there was a mapping of type
[[geo-sorting]]
==== Geo Distance Sorting
Allow to sort by `_geo_distance`. Here is an example:
Allow to sort by `_geo_distance`. Here is an example, assuming `pin.location` is a field of type `geo_point`:
[source,js]
--------------------------------------------------
@ -243,7 +243,7 @@ GET /_search
How to compute the distance. Can either be `sloppy_arc` (default), `arc` (slightly more precise but significantly slower) or `plane` (faster, but inaccurate on long distances and close to the poles).
`sort_mode`::
`mode`::
What to do in case a field has several geo points. By default, the shortest
distance is taken into account when sorting in ascending order and the