[DOCS] rewrite -> fuzzy_rewrite in match query
Fixed typo
This commit is contained in:
parent
b5adc877ca
commit
39705aa236
|
@ -185,7 +185,7 @@ sensitive which means that it depends on the type of the field being queried:
|
||||||
==== Numeric, date and IPv4 fields
|
==== Numeric, date and IPv4 fields
|
||||||
|
|
||||||
When querying numeric, date and IPv4 fields, `fuzziness` is interpreted as a
|
When querying numeric, date and IPv4 fields, `fuzziness` is interpreted as a
|
||||||
`+/- margin. It behaves like a <<query-dsl-range-query>> where:
|
`+/-` margin. It behaves like a <<query-dsl-range-query>> where:
|
||||||
|
|
||||||
-fuzziness <= field value <= +fuzziness
|
-fuzziness <= field value <= +fuzziness
|
||||||
|
|
||||||
|
|
|
@ -41,7 +41,7 @@ The `prefix_length` and
|
||||||
`max_expansions` can be set in this case to control the fuzzy process.
|
`max_expansions` can be set in this case to control the fuzzy process.
|
||||||
If the fuzzy option is set the query will use `constant_score_rewrite`
|
If the fuzzy option is set the query will use `constant_score_rewrite`
|
||||||
as its <<query-dsl-multi-term-rewrite,rewrite
|
as its <<query-dsl-multi-term-rewrite,rewrite
|
||||||
method>> the `rewrite` parameter allows to control how the query will get
|
method>> the `fuzzy_rewrite` parameter allows to control how the query will get
|
||||||
rewritten.
|
rewritten.
|
||||||
|
|
||||||
Here is an example when providing additional parameters (note the slight
|
Here is an example when providing additional parameters (note the slight
|
||||||
|
|
Loading…
Reference in New Issue