Skip to content

Commit 3e914a3

Browse files
author
Christoph Büscher
committed
[DOCS] Improve tip about updating search_analyzer (#69621)
The tip about updating a `search_analyzer` currently does not mention that most of the time (when the current analyzer is not "default"), user need to repeat the currently set "analyzer" parameter in the field definition. Adding this as a short note.
1 parent ac9e1e6 commit 3e914a3

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/reference/mapping/params/search-analyzer.asciidoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ the terms in the inverted index.
77

88
Sometimes, though, it can make sense to use a different analyzer at search
99
time, such as when using the <<analysis-edgengram-tokenizer,`edge_ngram`>>
10-
tokenizer for autocomplete.
10+
tokenizer for autocomplete or when using search-time synonyms.
1111

1212
By default, queries will use the `analyzer` defined in the field mapping, but
1313
this can be overridden with the `search_analyzer` setting:
@@ -76,4 +76,5 @@ See {defguide}/_index_time_search_as_you_type.html[Index time search-as-you-
7676
type] for a full explanation of this example.
7777

7878
TIP: The `search_analyzer` setting can be updated on existing fields
79-
using the <<indices-put-mapping,PUT mapping API>>.
79+
using the <<indices-put-mapping,PUT mapping API>>. Note, that in order to do so,
80+
any existing "analyzer" setting and "type" need to be repeated in the updated field definition.

0 commit comments

Comments
 (0)