[DOCS] Fuzzy wildcard not supported in `query_string` (#50466)
The `query_string` does not support mixing wildcards with fuzziness. This adds a related warning to the `query_string` docs.
This commit is contained in:
parent
1f6c1df58e
commit
de6b62f789
|
@ -44,6 +44,7 @@ You can specify fields to search in the query syntax:
|
|||
|
||||
_exists_:title
|
||||
|
||||
[[query-string-wildcard]]
|
||||
====== Wildcards
|
||||
|
||||
Wildcard searches can be run on individual terms, using `?` to replace
|
||||
|
@ -112,6 +113,7 @@ Elasticsearch to visit every term in the index:
|
|||
Use with caution!
|
||||
=======
|
||||
|
||||
[[query-string-fuzziness]]
|
||||
====== Fuzziness
|
||||
|
||||
We can search for terms that are
|
||||
|
@ -132,6 +134,16 @@ sufficient to catch 80% of all human misspellings. It can be specified as:
|
|||
|
||||
quikc~1
|
||||
|
||||
[[avoid-widlcards-fuzzy-searches]]
|
||||
[WARNING]
|
||||
.Avoid mixing fuzziness with wildcards
|
||||
====
|
||||
Mixing <<fuzziness,fuzzy>> and <<query-string-wildcard,wildcard>> operators is
|
||||
_not_ supported. When mixed, one of the operators is not applied. For example,
|
||||
you can search for `app~1` (fuzzy) or `app*` (wildcard), but searches for
|
||||
`app*~1` do not apply the fuzzy operator (`~1`).
|
||||
====
|
||||
|
||||
====== Proximity searches
|
||||
|
||||
While a phrase query (eg `"john smith"`) expects all of the terms in exactly
|
||||
|
|
Loading…
Reference in New Issue