From 4d29425f18157c6f6fd48d467ea84731405ff610 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christoph=20B=C3=BCscher?= Date: Wed, 27 Jun 2018 12:00:59 +0200 Subject: [PATCH] [Docs] Clarify accepted sort case Rescore only works with an explicite "sort" element if it is on descending "_score". Even using "order" : "asc" will throw an error. --- docs/reference/search/request/rescore.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/search/request/rescore.asciidoc b/docs/reference/search/request/rescore.asciidoc index 6e1bb2a9e6ce2..6c03aa70e9927 100644 --- a/docs/reference/search/request/rescore.asciidoc +++ b/docs/reference/search/request/rescore.asciidoc @@ -15,8 +15,8 @@ Currently the rescore API has only one implementation: the query rescorer, which uses a query to tweak the scoring. In the future, alternative rescorers may be made available, for example, a pair-wise rescorer. -NOTE: An error will be thrown if an explicit <> (other than `_score`) -is provided with a `rescore` query. +NOTE: An error will be thrown if an explicit <> +(other than `_score` in descending order) is provided with a `rescore` query. NOTE: when exposing pagination to your users, you should not change `window_size` as you step through each page (by passing different