Skip to content

Commit 7878353

Browse files
docs updated
1 parent a648c57 commit 7878353

File tree

2 files changed

+14
-12
lines changed

2 files changed

+14
-12
lines changed

advanced_usage_examples.rst

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1767,11 +1767,13 @@ ViewSet definition
17671767
Functional suggesters for the view are configured in
17681768
``functional_suggester_fields`` property.
17691769

1770-
In the example below, the ``title_suggest_prefix`` is the name of the GET query
1770+
In the example below, the ``title_suggest`` is the name of the GET query
17711771
param which points to the ``title.raw`` field of the ``BookDocument`` document.
1772-
For the ``title_suggest`` the allowed suggesters are
1773-
``FUNCTIONAL_SUGGESTER_COMPLETION_PREFIX`` and
1774-
``FUNCTIONAL_SUGGESTER_COMPLETION_MATCH``.
1772+
For the ``title_suggest`` the allowed suggester is
1773+
``FUNCTIONAL_SUGGESTER_COMPLETION_PREFIX``. For Ngram match we have the
1774+
``title_suggest_match`` field, which points to ``title.edge_ngram_completion``
1775+
field of the same document. For ``title_suggest_match`` the allowed suggester
1776+
is ``FUNCTIONAL_SUGGESTER_COMPLETION_MATCH``.
17751777

17761778
URL shall be constructed in the following way:
17771779

@@ -1843,11 +1845,10 @@ functionality). Thus, it might be written as short as:
18431845
18441846
# Functional suggester fields
18451847
functional_suggester_fields = {
1846-
'title_suggest_prefix': {
1848+
'title_suggest': {
18471849
'field': 'title.raw',
18481850
'suggesters': [
18491851
FUNCTIONAL_SUGGESTER_COMPLETION_PREFIX,
1850-
FUNCTIONAL_SUGGESTER_COMPLETION_MATCH,
18511852
],
18521853
'default_suggester': FUNCTIONAL_SUGGESTER_COMPLETION_PREFIX,
18531854
},

docs/advanced_usage_examples.rst

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1767,11 +1767,13 @@ ViewSet definition
17671767
Functional suggesters for the view are configured in
17681768
``functional_suggester_fields`` property.
17691769

1770-
In the example below, the ``title_suggest_prefix`` is the name of the GET query
1770+
In the example below, the ``title_suggest`` is the name of the GET query
17711771
param which points to the ``title.raw`` field of the ``BookDocument`` document.
1772-
For the ``title_suggest`` the allowed suggesters are
1773-
``FUNCTIONAL_SUGGESTER_COMPLETION_PREFIX`` and
1774-
``FUNCTIONAL_SUGGESTER_COMPLETION_MATCH``.
1772+
For the ``title_suggest`` the allowed suggester is
1773+
``FUNCTIONAL_SUGGESTER_COMPLETION_PREFIX``. For Ngram match we have the
1774+
``title_suggest_match`` field, which points to ``title.edge_ngram_completion``
1775+
field of the same document. For ``title_suggest_match`` the allowed suggester
1776+
is ``FUNCTIONAL_SUGGESTER_COMPLETION_MATCH``.
17751777

17761778
URL shall be constructed in the following way:
17771779

@@ -1843,11 +1845,10 @@ functionality). Thus, it might be written as short as:
18431845
18441846
# Functional suggester fields
18451847
functional_suggester_fields = {
1846-
'title_suggest_prefix': {
1848+
'title_suggest': {
18471849
'field': 'title.raw',
18481850
'suggesters': [
18491851
FUNCTIONAL_SUGGESTER_COMPLETION_PREFIX,
1850-
FUNCTIONAL_SUGGESTER_COMPLETION_MATCH,
18511852
],
18521853
'default_suggester': FUNCTIONAL_SUGGESTER_COMPLETION_PREFIX,
18531854
},

0 commit comments

Comments
 (0)