Update Fuzzy Query docs to clarify default behavior re max_expansions (#30819)
Stating that the Fuzzy Query generates "all possible" matching terms is misleading, given that the query's default behavior is to generate a maximum of 50 matching terms. (cherry picked from commit 345a0071a2a41fd7f80ae9ef8a39a2cb4991aedd)
This commit is contained in:
parent
cf7489899a
commit
072c0be8af
|
@ -5,10 +5,10 @@ The fuzzy query uses similarity based on Levenshtein edit distance.
|
||||||
|
|
||||||
==== String fields
|
==== String fields
|
||||||
|
|
||||||
The `fuzzy` query generates all possible matching terms that are within the
|
The `fuzzy` query generates matching terms that are within the
|
||||||
maximum edit distance specified in `fuzziness` and then checks the term
|
maximum edit distance specified in `fuzziness` and then checks the term
|
||||||
dictionary to find out which of those generated terms actually exist in the
|
dictionary to find out which of those generated terms actually exist in the
|
||||||
index.
|
index. The final query uses up to `max_expansions` matching terms.
|
||||||
|
|
||||||
Here is a simple example:
|
Here is a simple example:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue