[DOCS] Added a few clarifications to the docs from the issues list
This commit is contained in:
parent
94be785726
commit
9f5d0b6e89
|
@ -139,9 +139,10 @@ only new fields will not be introduced into the mapping, parsing
|
|||
[float]
|
||||
==== enabled
|
||||
|
||||
The `enabled` flag allows to disable parsing and adding a named object
|
||||
completely. This is handy when a portion of the JSON document passed
|
||||
should not be indexed. For example:
|
||||
The `enabled` flag allows to disable parsing and indexing a named object
|
||||
completely. This is handy when a portion of the JSON document contains
|
||||
arbitrary JSON which should not be indexed, nor added to the mapping.
|
||||
For example:
|
||||
|
||||
[source,js]
|
||||
--------------------------------------------------
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
[[query-dsl-fuzzy-query]]
|
||||
=== Fuzzy Query
|
||||
|
||||
A fuzzy based query that uses similarity based on Levenshtein (edit
|
||||
distance) algorithm.
|
||||
A fuzzy query that uses similarity based on Levenshtein (edit
|
||||
distance) algorithm. This maps to Lucene's `FuzzyQuery`.
|
||||
|
||||
Warning: this query is not very scalable with its default prefix length
|
||||
of 0 - in this case, *every* term will be enumerated and cause an edit
|
||||
|
|
|
@ -37,6 +37,9 @@ The query is optional, and when not provided, it will use `match_all` to
|
|||
count all the docs.
|
||||
|
||||
|
||||
NOTE: in contrast to <<search-search>> the query being sent in the body must
|
||||
*not* be nested in a `query` key.
|
||||
|
||||
[float]
|
||||
=== Multi index, Multi type
|
||||
|
||||
|
|
Loading…
Reference in New Issue