WARNING: Version 5.6 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Data is not always clean. Depending on how it is produced a number might be
rendered in the JSON body as a true JSON number, e.g.
5, but it might also
be rendered as a string, e.g.
"5". Alternatively, a number that should be
an integer might instead be rendered as a floating point, e.g.
5.0, or even
Coercion attempts to clean up dirty values to fit the datatype of a field. For instance:
- Strings will be coerced to numbers.
- Floating points will be truncated for integer values.
This document will be rejected because coercion is disabled.
coerce setting is allowed to have different settings for fields of
the same name in the same index. Its value can be updated on existing fields
using the PUT mapping API.
index.mapping.coerce setting can be set on the index level to disable
coercion globally across all mapping types: