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/elasticsearch/mapping-reference/sparse-vector.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,7 @@ PUT my-index
24
24
}
25
25
```
26
26
27
+
{applies_to}`stack: preview 9.1`
27
28
With any new indices created, token pruning will be turned on by default with appropriate defaults. You can control this behaviour using the optional `index_options` parameters for the field:
28
29
29
30
```console
@@ -58,8 +59,8 @@ The following parameters are accepted by `sparse_vector` fields:
58
59
* Exclude the field from [_source](/reference/elasticsearch/rest-apis/retrieve-selected-fields.md#source-filtering).
59
60
* Use [synthetic `_source`](/reference/elasticsearch/mapping-reference/mapping-source-field.md#synthetic-source).
60
61
61
-
index_options
62
-
: (Optional, object) You can set index options for your `sparse_vector` field to determine if you should prune tokens, and the parameter configurations for the token pruning. If pruning options are not set in your `sparse_query`vector, Elasticsearch will use the default options configured for the field, if any. The available options for the index options are:
62
+
index_options {applies_to}`stack: preview 9.1`
63
+
: (Optional, object) You can set index options for your `sparse_vector` field to determine if you should prune tokens, and the parameter configurations for the token pruning. If pruning options are not set in your [`sparse_vector` query](/reference/query-languages/query-dsl/query-dsl-sparse-vector-query.md), Elasticsearch will use the default options configured for the field, if any.
63
64
64
65
Parameters for `index_options` are:
65
66
@@ -87,7 +88,9 @@ Non-significant tokens can be defined as tokens that meet both of the following
87
88
* The weight/score is so low that the token is likely not very relevant to the original term
88
89
89
90
Both the token frequency threshold and weight threshold must show the token is non-significant in order for the token to be pruned.
90
-
This ensures the tokens that are kept are frequent enough and have very high scoring or very infrequent tokens that may not have as high of a score.
91
+
This ensures that:
92
+
* The tokens that are kept are frequent enough and have significant scoring.
93
+
* Very infrequent tokens that may not have as high of a score are removed.
0 commit comments