From ad7c22198ce6c202b874da59c2ee43bf11a749e7 Mon Sep 17 00:00:00 2001 From: Martijn van Groningen Date: Thu, 22 Sep 2016 10:00:11 +0000 Subject: [PATCH] docs: describe more explicitly what happens when indexing queries that fetch terms --- docs/reference/mapping/types/percolator.asciidoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/reference/mapping/types/percolator.asciidoc b/docs/reference/mapping/types/percolator.asciidoc index ca8c8386e9b..65f0d72550e 100644 --- a/docs/reference/mapping/types/percolator.asciidoc +++ b/docs/reference/mapping/types/percolator.asciidoc @@ -82,4 +82,7 @@ time (using `now`). There are a number of queries that fetch data via a get call during query parsing. For example the `terms` query when using terms lookup, `template` query when using indexed scripts and `geo_shape` when using pre-indexed shapes. When these queries are indexed by the `percolator` field type then the get call is executed once. So each time the `percolator` -query evaluates these queries, the fetches terms, shapes etc. as the were upon index time will be used. \ No newline at end of file +query evaluates these queries, the fetches terms, shapes etc. as the were upon index time will be used. Important to note +is that fetching of terms that these queries do, happens both each time the percolator query gets indexed on both primary +and replica shards, so the terms that are actually indexed can be different between shard copies, if the source index +changed while indexing. \ No newline at end of file