org.elasticsearch.index.mapper.MapperParsingException: failed to parse [error]

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips


Java does not handle IPv6 nameservers before 1.8.0_60. Upgrade to the latest JVM.

Expert tip

This is a bug in Wise, updating to v4.10 seems to solve the problem.

Solutions on the web

via GitHub by Nycander
, 2 years ago
failed to parse [value]
via GitHub by Backenkoehler
, 1 year ago
failed to parse [datetime]
via by Unknown author, 2 years ago
java.lang.NumberFormatException: For input string: "Cached ad is better"
at java.lang.NumberFormatException.forInputString(
at java.lang.Long.parseLong(
at java.lang.Long.parseLong(
at org.elasticsearch.index.mapper.core.LongFieldMapper.innerParseCreateField(
at org.elasticsearch.index.mapper.core.NumberFieldMapper.parseCreateField(
at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(
at org.elasticsearch.index.mapper.object.ObjectMapper.serializeValue(
at org.elasticsearch.index.mapper.object.ObjectMapper.parse(
at org.elasticsearch.index.mapper.DocumentMapper.parse(
at org.elasticsearch.index.mapper.DocumentMapper.parse(
at org.elasticsearch.index.shard.IndexShard.prepareCreate(
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation(
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

Users with the same issue

4 times, 1 day ago
Once, 2 days ago
4 times, 1 week ago
16 times, 1 week ago
6 times, 1 week ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.