honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-17 10:25:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #14871 from jamiemccarthy/doc-fix

Browse Source 
Fix doc of nested_path sort option
This commit is contained in:
Clinton Gormley 2015-11-28 17:46:47 +01:00
commit 174b4bacbe
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -84,13 +84,12 @@ field support has the following parameters on top of the already
existing sort options: existing sort options:
`nested_path`:: `nested_path`::
Defines the on what nested object to sort. The actual Defines on which nested object to sort. The actual
sort field must be a direct field inside this nested object. The default sort field must be a direct field inside this nested object.
is to use the most immediate inherited nested object from the sort When sorting by nested field, this field is mandatory.
field.
`nested_filter`:: `nested_filter`::
A filter the inner objects inside the nested path A filter that the inner objects inside the nested path
should match with in order for its field values to be taken into account should match with in order for its field values to be taken into account
by sorting. Common case is to repeat the query / filter inside the by sorting. Common case is to repeat the query / filter inside the
nested filter or query. By default no `nested_filter` is active. nested filter or query. By default no `nested_filter` is active.
@ -98,7 +97,7 @@ existing sort options:
===== Nested sorting example ===== Nested sorting example
In the below example `offer` is a field of type `nested`. In the below example `offer` is a field of type `nested`.
The `nested_path` needs to be specified other elasticsearch doesn't on what nested level sort values need to be captured. The `nested_path` needs to be specified; otherwise, elasticsearch doesn't know on what nested level sort values need to be captured.
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------