From 06cec760dad60437de989121b5bde3c3371ba914 Mon Sep 17 00:00:00 2001 From: junmuz Date: Mon, 13 Jan 2020 19:47:36 +0500 Subject: [PATCH] [DOCS] Correct typo in `ignore_malformed` mapping parm docs (#50780) --- docs/reference/mapping/params/ignore-malformed.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/mapping/params/ignore-malformed.asciidoc b/docs/reference/mapping/params/ignore-malformed.asciidoc index 9ea5be72bdb28..ab0869bd558fb 100644 --- a/docs/reference/mapping/params/ignore-malformed.asciidoc +++ b/docs/reference/mapping/params/ignore-malformed.asciidoc @@ -95,7 +95,7 @@ Malformed fields are silently ignored at indexing time when `ignore_malformed` is turned on. Whenever possible it is recommended to keep the number of documents that have a malformed field contained, or queries on this field will 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 `exists`,`term` or `terms` queries on the special <> field. [[json-object-limits]] @@ -111,4 +111,4 @@ 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 +and reject the entire document regardless of the `ignore_malformed` setting.