@@ -10,25 +10,27 @@ The `index_options` parameter is intended for use with <<text,`text`>> fields
10
10
only. Avoid using `index_options` with other field data types.
11
11
====
12
12
13
- It accepts the following values:
13
+ The parameter accepts one of the following values. Each value retrieves
14
+ information from the previous listed values. For example, `freqs` contains
15
+ `docs`; `positions` contains both `freqs` and `docs`.
14
16
15
17
`docs`::
16
- Only the doc number is indexed. Can answer the question _Does this term
17
- exist in this field?_
18
+ Only the doc number is indexed. Can answer the question _Does this term exist in
19
+ this field?_
18
20
19
21
`freqs`::
20
- Doc number and term frequencies are indexed. Term frequencies are used to
21
- score repeated terms higher than single terms.
22
+ Doc number and term frequencies are indexed. Term frequencies are used to score
23
+ repeated terms higher than single terms.
22
24
23
25
`positions` (default)::
24
26
Doc number, term frequencies, and term positions (or order) are indexed.
25
- Positions can be used for
26
- <<query-dsl-match-query-phrase,proximity or phrase queries>>.
27
+ Positions can be used for <<query-dsl-match-query-phrase,proximity or phrase
28
+ queries>>.
27
29
28
30
`offsets`::
29
- Doc number, term frequencies, positions, and start and end character
30
- offsets (which map the term back to the original string) are indexed.
31
- Offsets are used by the <<unified-highlighter,unified highlighter>> to speed up highlighting.
31
+ Doc number, term frequencies, positions, and start and end character offsets
32
+ (which map the term back to the original string) are indexed. Offsets are used
33
+ by the <<unified-highlighter,unified highlighter>> to speed up highlighting.
32
34
33
35
[source,console]
34
36
--------------------------------------------------
0 commit comments