honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/master'

This commit is contained in:
David Pilato 2017-01-30 17:53:13 +01:00
parent 72e15b1c7c e7e871acdd
commit 4d1e291933
4 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/aggregations/bucket/geodistance-aggregation.asciidoc
View File

@ -83,7 +83,7 @@ By default, the distance unit is `m` (metres) but it can also accept: `mi` (mile
<1> The distances will be computed as miles
There are three distance calculation modes: `sloppy_arc` (the default), `arc` (most accurate) and `plane` (fastest). The `arc` calculation is the most accurate one but also the more expensive one in terms of performance. The `sloppy_arc` is faster but less accurate. The `plane` is the fastest but least accurate distance function. Consider using `plane` when your search context is "narrow" and spans smaller geographical areas (like cities or even countries). `plane` may return higher error mergins for searches across very large areas (e.g. cross continent search). The distance calculation type can be set using the `distance_type` parameter:
There are three distance calculation modes: `sloppy_arc` (the default), `arc` (most accurate) and `plane` (fastest). The `arc` calculation is the most accurate one but also the more expensive one in terms of performance. The `sloppy_arc` is faster but less accurate. The `plane` is the fastest but least accurate distance function. Consider using `plane` when your search context is "narrow" and spans smaller geographical areas (like cities or even countries). `plane` may return higher error margins for searches across very large areas (e.g. cross continent search). The distance calculation type can be set using the `distance_type` parameter:
[source,js]
--------------------------------------------------

4
docs/reference/migration/migrate_6_0/search.asciidoc
View File

@ -48,7 +48,7 @@ have any effect in previous versions.
==== Scoring changes
==== Query normalization
===== Query normalization
Query normalization has been removed. This means that the TF-IDF similarity no
longer tries to make scores comparable across queries and that boosts are now
@ -60,7 +60,7 @@ already integrated boosts into scores as multiplicative factors.
See https://issues.apache.org/jira/browse/LUCENE-7347[`LUCENE-7347`] for more
information.
==== Coordination factors
===== Coordination factors
Coordination factors have been removed from the scoring formula. This means that
boolean queries no longer score based on the number of matching clauses.

2
docs/reference/search/request-body.asciidoc
View File

@ -183,4 +183,6 @@ include::request/named-queries-and-filters.asciidoc[]
include::request/inner-hits.asciidoc[]
include::request/collapse.asciidoc[]
include::request/search-after.asciidoc[]

6
docs/reference/search/request/collapse.asciidoc
View File

@ -1,5 +1,5 @@
[[search-request-collapse]]
== Collapse
=== Field Collapsing
Allows to collapse search results based on field values.
The collapsing is done by selecting only the top sorted document per collapse key.
@ -30,12 +30,12 @@ GET /twitter/tweet/_search
WARNING: The total number of hits in the response indicates the number of matching documents without collapsing.
The total number of distinct group is unknown.
The field used for collapsing must be a single valued <<keyword, `keyword`> or <<number, `number`>> field with <<doc-values, `doc_values`>> activated
The field used for collapsing must be a single valued <<keyword, `keyword`>> or <<number, `numeric`>> field with <<doc-values, `doc_values`>> activated
NOTE: The collapsing is applied to the top hits only and does not affect aggregations.
=== Expand collapse results
==== Expand collapse results
It is also possible to expand each collapsed top hits with the `inner_hits` option.