From 0fb81d664367b0724c6ca2ad067e2befabc6fd9b Mon Sep 17 00:00:00 2001 From: Sergii Golubev Date: Fri, 26 Sep 2014 13:58:12 +0300 Subject: [PATCH] Docs: Update id-field.asciidoc It is strange to provide an example with `"store" : false` when talking about possibility of enabling the field to be stored. Broke the line in the mapping in two lines for better readability. More verbose sentence above the mapping. Closes #7894 --- docs/reference/mapping/fields/id-field.asciidoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/reference/mapping/fields/id-field.asciidoc b/docs/reference/mapping/fields/id-field.asciidoc index 1adab49796a..5867d07b95c 100644 --- a/docs/reference/mapping/fields/id-field.asciidoc +++ b/docs/reference/mapping/fields/id-field.asciidoc @@ -11,13 +11,16 @@ using `term`, `terms` or `prefix` queries/filters (including the specific `ids` query/filter). The `_id` field can be enabled to be indexed, and possibly stored, -using: +using the appropriate mapping attributes: [source,js] -------------------------------------------------- { "tweet" : { - "_id" : {"index": "not_analyzed", "store" : false } + "_id" : { + "index" : "not_analyzed", + "store" : true + } } } --------------------------------------------------