From 20ece4acb5d85143dfb78e911e4dd2b3798ff918 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Thu, 12 Feb 2015 12:09:18 +0100 Subject: [PATCH] Update core-types.asciidoc Provide an example of how to disable norms Closes #9641 --- .../mapping/types/core-types.asciidoc | 23 ++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/docs/reference/mapping/types/core-types.asciidoc b/docs/reference/mapping/types/core-types.asciidoc index 6226e73f543..981bb885874 100644 --- a/docs/reference/mapping/types/core-types.asciidoc +++ b/docs/reference/mapping/types/core-types.asciidoc @@ -181,9 +181,26 @@ norms on it. In particular, this is the case for fields that are used solely for filtering or aggregations. 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 -or updates, and segments get merged. Any score computation on a field that got +by using the <>, like this: + +[source,json] +------------ +PUT my_index/_mapping/my_type +{ + "properties": { + "title": { + "type": "string", + "norms": { + "enabled": false + } + } + } +} +------------ + +Please however note that norms won't be removed instantly, but will be removed +as old segments are merged into new segments as you continue indexing new documents. +Any score computation on a field that has had norms removed might return inconsistent results since some documents won't have norms anymore while other documents might still have norms.