From c977a49b76c37453ebaf267f51fb359dd03e8359 Mon Sep 17 00:00:00 2001 From: Adrien Grand Date: Tue, 25 Mar 2014 16:05:23 +0100 Subject: [PATCH] [DOC] Clarify settings and documentation about norms. --- docs/reference/mapping/types/core-types.asciidoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/reference/mapping/types/core-types.asciidoc b/docs/reference/mapping/types/core-types.asciidoc index 60882fdeff9..1dd2e9d959f 100644 --- a/docs/reference/mapping/types/core-types.asciidoc +++ b/docs/reference/mapping/types/core-types.asciidoc @@ -110,11 +110,11 @@ Automatically set to `true` when the fielddata format is `doc_values`. `null_value` as the field value. Defaults to not adding the field at all. -|`norms.enabled` |Boolean value if norms should be enabled or not. Defaults -to `true` for `analyzed` fields, and to `false` for `not_analyzed` fields. -See the <>. +|`norms: {enabled: }` |Boolean value if norms should be enabled or +not. Defaults to `true` for `analyzed` fields, and to `false` for +`not_analyzed` fields. See the <>. -|`norms.loading` |Describes how norms should be loaded, possible values are +|`norms: {loading: }` |Describes how norms should be loaded, possible values are `eager` and `lazy` (default). It is possible to change the default value to eager for all fields by configuring the index setting `index.norms.loading` to `eager`. @@ -181,6 +181,7 @@ you don't need scoring on a specific field, it is highly recommended to disable norms on it. In particular, this is the case for fields that are used solely for filtering or aggregations. +coming[1.2.0] In case you would like to disable norms after the fact, it is possible to do so by using the <>. Please however note that norms won't be removed instantly, but as your index will receive new insertions