| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667 | [[index-options]]=== `index_options`The `index_options` parameter controls what information is added to theinverted index for search and highlighting purposes.[WARNING]====The `index_options` parameter is intended for use with <<text,`text`>> fieldsonly. Avoid using `index_options` with other field data types.====It accepts the following values:`docs`::Only the doc number is indexed.  Can answer the question _Does this termexist in this field?_`freqs`::Doc number and term frequencies are indexed.  Term frequencies are used toscore repeated terms higher than single terms.`positions` (default)::Doc number, term frequencies, and term positions (or order) are indexed.Positions can be used for<<query-dsl-match-query-phrase,proximity or phrase queries>>.`offsets`::Doc number, term frequencies, positions, and start and end characteroffsets (which map the term back to the original string) are indexed.Offsets are used by the <<unified-highlighter,unified highlighter>> to speed up highlighting.[source,console]--------------------------------------------------PUT my-index-000001{  "mappings": {    "properties": {      "text": {        "type": "text",        "index_options": "offsets"      }    }  }}PUT my-index-000001/_doc/1{  "text": "Quick brown fox"}GET my-index-000001/_search{  "query": {    "match": {      "text": "brown fox"    }  },  "highlight": {    "fields": {      "text": {} <1>    }  }}--------------------------------------------------<1> The `text` field will use the postings for the highlighting by default because `offsets` are indexed.
 |