From 999462f46082c2ab851d5ea91c42e63622299e20 Mon Sep 17 00:00:00 2001 From: James Rodewig Date: Wed, 10 Apr 2019 14:46:51 -0400 Subject: [PATCH] [DOCS] Document limits for JSON objects with `ignore_malformed` mapping setting (#40976) --- .../mapping/params/ignore-malformed.asciidoc | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/reference/mapping/params/ignore-malformed.asciidoc b/docs/reference/mapping/params/ignore-malformed.asciidoc index 30aa6c4e8bc..f8f9a4591f9 100644 --- a/docs/reference/mapping/params/ignore-malformed.asciidoc +++ b/docs/reference/mapping/params/ignore-malformed.asciidoc @@ -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 <> field. +==== Limits for JSON Objects +You can't use `ignore_malformed` with the following 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. \ No newline at end of file