From b940bac10c3b791662d7268b87db94e15c45782a Mon Sep 17 00:00:00 2001 From: Ryan Ernst Date: Tue, 5 May 2015 17:48:54 -0700 Subject: [PATCH] address PR comments --- docs/reference/mapping/fields/field-names-field.asciidoc | 1 - docs/reference/mapping/fields/routing-field.asciidoc | 6 ++---- 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/docs/reference/mapping/fields/field-names-field.asciidoc b/docs/reference/mapping/fields/field-names-field.asciidoc index f98dc6ccb24de..4f3e4a2b3fb87 100644 --- a/docs/reference/mapping/fields/field-names-field.asciidoc +++ b/docs/reference/mapping/fields/field-names-field.asciidoc @@ -1,6 +1,5 @@ [[mapping-field-names-field]] === `_field_names` -added[1.3.0] The `_field_names` field indexes the field names of a document, which can later be used to search for documents based on the fields that they contain typically diff --git a/docs/reference/mapping/fields/routing-field.asciidoc b/docs/reference/mapping/fields/routing-field.asciidoc index 6ca0561359896..37b173e5aa365 100644 --- a/docs/reference/mapping/fields/routing-field.asciidoc +++ b/docs/reference/mapping/fields/routing-field.asciidoc @@ -2,7 +2,7 @@ === `_routing` The routing field allows to control the `_routing` aspect when indexing -data and explicit routing control is required. +data and explicit routing control is required. It is stored and indexed. [float] ==== required @@ -11,9 +11,7 @@ Another aspect of the `_routing` mapping is the ability to define it as required by setting `required` to `true`. This is very important to set when using routing features, as it allows different APIs to make use of it. For example, an index operation will be rejected if no routing value -has been provided (or derived from the doc). A delete operation will be -broadcasted to all shards if no routing value is provided and `_routing` -is required. +has been provided. [float] ==== id uniqueness