From 288217e82bfd1267107afdd5b5b082a0b9787f92 Mon Sep 17 00:00:00 2001 From: Antoine Garcia Date: Mon, 18 Nov 2019 16:37:51 +0100 Subject: [PATCH] =?UTF-8?q?[Docs]=C2=A0Specify=20field=20types=20not=20sup?= =?UTF-8?q?porting=20doc=20values=20(#49041)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The `string` type (with option `analyzed`) has been replaced by `text` after `6.0`, also the `annonated_text` field do not support doc values and should be mentioned. --- docs/reference/mapping/params/doc-values.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/mapping/params/doc-values.asciidoc b/docs/reference/mapping/params/doc-values.asciidoc index 53d6ac9ebdd..63e583e71c6 100644 --- a/docs/reference/mapping/params/doc-values.asciidoc +++ b/docs/reference/mapping/params/doc-values.asciidoc @@ -15,7 +15,7 @@ Doc values are the on-disk data structure, built at document index time, which makes this data access pattern possible. They store the same values as the `_source` but in a column-oriented fashion that is way more efficient for sorting and aggregations. Doc values are supported on almost all field types, -with the __notable exception of `analyzed` string fields__. +with the __notable exception of `text` and `annotated_text` fields__. All fields which support doc values have them enabled by default. If you are sure that you don't need to sort or aggregate on a field, or access the field