You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/query-languages/esql/_snippets/commands/layout/rerank.md
+20-21Lines changed: 20 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,14 +7,13 @@ stack: preview 9.2.0
7
7
The `RERANK` command uses an inference model to compute a new relevance score
8
8
for an initial set of documents, directly within your ES|QL queries.
9
9
10
-
:::::{important}
11
-
**RERANK processes each row through an inference model, which impacts performance and costs.**
10
+
::::{tab-set}
12
11
13
-
::::{applies-switch}
12
+
:::{tab-item} 9.3.0+
14
13
15
-
:::{applies-item} stack: ga 9.3+
16
-
17
-
`RERANK`automatically limits processing to **1000 rows by default** to prevent accidental high consumption. This limit is applied before the `RERANK` command executes.
14
+
Starting in version 9.3.0, `RERANK` automatically limits processing to **1000
15
+
rows by default** to prevent accidental high consumption. This limit is applied
16
+
before the `RERANK` command executes.
18
17
19
18
If you need to process more rows, you can adjust the limit using the cluster setting:
20
19
```
@@ -37,7 +36,7 @@ PUT _cluster/settings
37
36
```
38
37
:::
39
38
40
-
:::{applies-item} stack: ga =9.2
39
+
:::{tab-item} 9.2.x
41
40
42
41
No automatic row limit is applied. **You should always use `LIMIT` before or after `RERANK` to control the number of documents processed**, to avoid accidentally reranking large datasets which can result in high latency and increased costs.
43
42
@@ -52,7 +51,6 @@ FROM books
52
51
:::
53
52
54
53
::::
55
-
:::::
56
54
57
55
**Syntax**
58
56
@@ -108,36 +106,31 @@ necessary.
108
106
109
107
How you increase the timeout depends on your deployment type:
110
108
111
-
::::::{applies-switch}
112
-
113
-
:::::{applies-item} ess:
109
+
::::{tab-set}
110
+
:::{tab-item} {{ech}}
114
111
115
112
* You can adjust {{es}} settings in
116
113
the [Elastic Cloud Console](docs-content://deploy-manage/deploy/elastic-cloud/edit-stack-settings.md)
117
114
* You can also adjust the `search.default_search_timeout` cluster setting
118
115
using [Kibana's Advanced settings](kibana://reference/advanced-settings.md#kibana-search-settings)
116
+
:::
119
117
120
-
:::::
121
-
122
-
:::::{applies-item} self:
118
+
:::{tab-item} Self-managed
123
119
124
120
* You can configure at the cluster level by setting
125
121
`search.default_search_timeout`in `elasticsearch.yml` or updating
126
122
via [Cluster Settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings)
127
123
* You can also adjust the `search:timeout` setting
128
124
using [Kibana's Advanced settings](kibana://reference/advanced-settings.md#kibana-search-settings)
129
125
* Alternatively, you can add timeout parameters to individual queries
126
+
:::
130
127
131
-
:::::
132
-
133
-
:::::{applies-item} serverless:
128
+
:::{tab-item} {{serverless-full}}
134
129
135
130
* Requires a manual override from Elastic Support because you cannot modify
136
131
timeout settings directly
137
-
138
-
:::::
139
-
140
-
::::::
132
+
:::
133
+
::::
141
134
142
135
If you don't want to increase the timeout limit, try the following:
143
136
@@ -165,3 +158,9 @@ Combine the original score with the reranked score:
0 commit comments