Update rescoring docs in respect to sort (#20477)

* Update rescoring docs in respect to sort

If sort is present in a query the rescore query is not executed. As long as this feature is neither implemented (see discussion in #6788) nor  the combination of sort and rescoring raises an error, we should warn the user in the documentation about this.

* Missed a dot
This commit is contained in:
Tobias Günther 2016-09-14 18:05:36 +02:00 committed by Clinton Gormley
parent bb6e7eeb7a
commit 3a7a437594
1 changed files with 3 additions and 1 deletions

View File

@ -12,9 +12,11 @@ A `rescore` request is executed on each shard before it returns its
results to be sorted by the node handling the overall search request. results to be sorted by the node handling the overall search request.
Currently the rescore API has only one implementation: the query Currently the rescore API has only one implementation: the query
rescorer, which uses a query to tweak the scoring. In the future, rescorer, which uses a query to tweak the scoring. In the future,
alternative rescorers may be made available, for example, a pair-wise rescorer. alternative rescorers may be made available, for example, a pair-wise rescorer.
NOTE: the `rescore` phase is not executed when <<search-request-sort,`sort`>> is used.
NOTE: when exposing pagination to your users, you should not change NOTE: when exposing pagination to your users, you should not change
`window_size` as you step through each page (by passing different `window_size` as you step through each page (by passing different
`from` values) since that can alter the top hits causing results to `from` values) since that can alter the top hits causing results to