[DOCS] Document limits for JSON objects with `ignore_malformed` mapping setting (#40976)
This commit is contained in:
parent
a0b54a9a92
commit
999462f460
|
@ -91,3 +91,16 @@ become meaningless. Elasticsearch makes it easy to check how many documents
|
||||||
have malformed fields by using `exist` or `term` queries on the special
|
have malformed fields by using `exist` or `term` queries on the special
|
||||||
<<mapping-ignored-field,`_ignored`>> field.
|
<<mapping-ignored-field,`_ignored`>> field.
|
||||||
|
|
||||||
|
==== Limits for JSON Objects
|
||||||
|
You can't use `ignore_malformed` with the following datatypes:
|
||||||
|
|
||||||
|
* <<nested, Nested datatype>>
|
||||||
|
* <<object, Object datatype>>
|
||||||
|
* <<range, Range datatypes>>
|
||||||
|
|
||||||
|
You also can't use `ignore_malformed` to ignore JSON objects submitted to fields
|
||||||
|
of the wrong datatype. A JSON object is any data surrounded by curly brackets
|
||||||
|
`"{}"` and includes data mapped to the nested, object, and range datatypes.
|
||||||
|
|
||||||
|
If you submit a JSON object to an unsupported field, {es} will return an error
|
||||||
|
and reject the entire document regardless of the `ignore_malformed` setting.
|
Loading…
Reference in New Issue