[DOCS] Document limits for JSON objects with ignore_malformed mapping setting

[jrodewig]

As of this writing,ignore_malformed has two undocumented limits for JSON objects:

• ignore_malformed does not support datatypes intended for JSON objects, like range or object
• Other field types support ignore_malformed for any JSON data format except JSON objects

This documents those limits. As #12366 notes, support for JSON objects may be added later. We can remove this section then.

Resolves #36464.

[elasticmachine]

Pinging @elastic/es-search

[bczifra]

The change says:

You can't use ignore_malformed to index JSON objects into field datatypes used
for other data formats, like text or integer.

ignore_malformed isn't used to index values. As the docs currently indicate:

The ignore_malformed parameter, if set to true, allows the exception to be ignored. The malformed field is not indexed, but other fields in the document are processed normally.

Thus, this should be something more like:

You can't use `ignore_malformed` to ignore JSON objects submitted for indexing against fields that were not mapped as objects, nested objects, or ranges. The field will not be ignored, the document will not be indexed, and instead an error will be returned for the indexing request.

I don't know whether this limitation is restricted to object, nested object, and range mappings, or whether there are any additional types for which this should be documented.

[jrodewig]

Thanks for your feedback @bczifra. I particularly appreciate you catching that use of index.

In 99f135d, I revised the section to highlight:

• The list of unsupported datatypes
• What we consider a JSON object (which includes the nested, object, and range mappings)
• Outcomes for submitting a JSON object to an unsupported field

I did some testing in 6.7 and confirmed the following with @jimczi:

• ignore_malformed does not support submitting any malformed data to nested, object, or range fields at all
• For fields mapped to other datatypes, ignore_malformed will work with any JSON data format except a JSON object. Data using the nested, object, or range mapping would be considered JSON objects.

[bczifra]

@jrodewig the changed text is great! Thanks for clarifying this!

[jrodewig]

@bczifra When convenient and if you approve, do you mind changing your review status from requested changes to approved? Thanks!

[jimczi]

LGTM

[bczifra]

LGTM