If a field was detected by Elasticsearch as a number (or a date) and an update (in an existing or new document) does not match the detected type for that field, Elasticsearch will fail in a way similar to this:
MapperParsingException[failed to parse [born]]; nested: NumberFormatException[For input string: \"abc\"];
We should add a way to have dynamic mapping (detect dates and numbers and index them as such, to enable range queries etc.) but ignore malformed entries without failing.
If a field was detected by Elasticsearch as a number (or a date) and an update (in an existing or new document) does not match the detected type for that field, Elasticsearch will fail in a way similar to this:
We should add a way to have dynamic mapping (detect dates and numbers and index them as such, to enable range queries etc.) but ignore malformed entries without failing.