From df9d4eca66a53c72aa5e9ab53f65a5b5b6da56d3 Mon Sep 17 00:00:00 2001 From: Alexander Pepper Date: Thu, 10 Sep 2015 11:13:02 +0200 Subject: [PATCH] [docs] Document meaning of "FST" and "FSTs". Conflicts: docs/reference/index-modules/fielddata.asciidoc --- .../search/suggesters/completion-suggest.asciidoc | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/reference/search/suggesters/completion-suggest.asciidoc b/docs/reference/search/suggesters/completion-suggest.asciidoc index ee8969b95e5..af93ea1598a 100644 --- a/docs/reference/search/suggesters/completion-suggest.asciidoc +++ b/docs/reference/search/suggesters/completion-suggest.asciidoc @@ -15,11 +15,12 @@ suggestion is, why you should use it at all, if you have prefix queries already. The answer is simple: Prefix suggestions are fast. The data structures are internally backed by Lucenes -`AnalyzingSuggester`, which uses FSTs to execute suggestions. Usually -these data structures are costly to create, stored in-memory and need to -be rebuilt every now and then to reflect changes in your indexed -documents. The `completion` suggester circumvents this by storing the -FST as part of your index during index time. This allows for really fast +`AnalyzingSuggester`, which uses FSTs (finite state transducers) to +execute suggestions. Usually these data structures are costly to +create, stored in-memory and need to be rebuilt every now and then to +reflect changes in your indexed documents. The `completion` suggester +circumvents this by storing the FST (finite state transducer) as part +of your index during index time. This allows for really fast loads and executions. [[completion-suggester-mapping]]