From a0c83c451120551dc34ced7b6f62fbaf2cb1a49c Mon Sep 17 00:00:00 2001 From: Alex Date: Tue, 17 Jan 2017 15:43:11 +0000 Subject: [PATCH] Minor doc changes to clarify mapping index param for string type (#22652) * Grammatical correction * Add note for legacy string mapping type * Update truncate token filter to not mention the keyword tokenizer The advice predates the existence of the keyword field Closes #22650 --- docs/reference/mapping/params/index.asciidoc | 1 + docs/reference/mapping/types/string.asciidoc | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/reference/mapping/params/index.asciidoc b/docs/reference/mapping/params/index.asciidoc index e097293d142..270c930e284 100644 --- a/docs/reference/mapping/params/index.asciidoc +++ b/docs/reference/mapping/params/index.asciidoc @@ -4,3 +4,4 @@ The `index` option controls whether field values are indexed. It accepts `true` or `false`. Fields that are not indexed are not queryable. +NOTE: For the legacy mapping type <> the `index` option only accepts legacy values `analyzed` (default, treat as full-text field), `not_analyzed` (treat as keyword field) and `no`. diff --git a/docs/reference/mapping/types/string.asciidoc b/docs/reference/mapping/types/string.asciidoc index b6a5fef86eb..c4be060cc40 100644 --- a/docs/reference/mapping/types/string.asciidoc +++ b/docs/reference/mapping/types/string.asciidoc @@ -12,7 +12,7 @@ to use `text` or `keyword`. Indexes imported from 2.x *only* support `string` and not `text` or `keyword`. To ease the migration from 2.x Elasticsearch will downgrade `text` and `keyword` -mappings applied to indexes imported to 2.x into `string`. While long lived +mappings applied to indexes imported from 2.x into `string`. While long lived indexes will eventually need to be recreated against 5.x before eventually upgrading to 6.x, this downgrading smooths the process before you find time for it.