From de6b62f78955993bb310cb8ad9ae60b2e4a9517a Mon Sep 17 00:00:00 2001 From: James Rodewig Date: Tue, 7 Jan 2020 12:53:47 -0600 Subject: [PATCH] [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. --- .../reference/query-dsl/query-string-syntax.asciidoc | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/reference/query-dsl/query-string-syntax.asciidoc b/docs/reference/query-dsl/query-string-syntax.asciidoc index 0f766f92dff..b59d9ef9adf 100644 --- a/docs/reference/query-dsl/query-string-syntax.asciidoc +++ b/docs/reference/query-dsl/query-string-syntax.asciidoc @@ -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 <> and <> 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