From 8430b379d889b7db6172f38548e5422044fd0766 Mon Sep 17 00:00:00 2001 From: Sergii Golubev Date: Tue, 5 Apr 2016 23:20:02 +0300 Subject: [PATCH] string.asciidoc: fix for `position_increment_gap` Remove outdated and duplicate description for the `position_increment_gap` parameter. --- docs/reference/mapping/types/text.asciidoc | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/reference/mapping/types/text.asciidoc b/docs/reference/mapping/types/text.asciidoc index 7798b2c41f0..4a5be8287e8 100644 --- a/docs/reference/mapping/types/text.asciidoc +++ b/docs/reference/mapping/types/text.asciidoc @@ -7,7 +7,7 @@ description of a product. These fields are `analyzed`, that is they are passed t before being indexed. The analysis process allows Elasticsearch to search for individual words _within_ each full text field. Text fields are not used for sorting and seldom used for aggregations (although the -<> +<> is a notable exception). If you need to index structured content such as email addresses, hostnames, status @@ -104,11 +104,9 @@ The following parameters are accepted by `text` fields: <>:: - The number of fake term positions which should be inserted between - each element of an array of strings. Defaults to 0. The number of fake term position which should be inserted between each - element of an array of strings. Defaults to the position_increment_gap - configured on the analyzer which defaults to 100. 100 was chosen because it + element of an array of strings. Defaults to the `position_increment_gap` + configured on the analyzer which defaults to `100`. `100` was chosen because it prevents phrase queries with reasonably large slops (less than 100) from matching terms across field values.