failed to parse

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web267

  • Failed to parse [_id]
  • failed to parse
  • failed to parse [_id]
  • Stack trace

    • org.elasticsearch.index.mapper.MapperParsingException: failed to parse at org.elasticsearch.index.mapper.DocumentMapper.parse( at org.elasticsearch.index.mapper.DocumentMapper.parse( at org.elasticsearch.index.shard.IndexShard.prepareIndex( at org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation( at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary( at$AsyncShardOperationAction.performOnPrimary( at$AsyncShardOperationAction$ at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at Caused by: org.elasticsearch.ElasticsearchParseException: field [lat] missing at org.elasticsearch.common.geo.GeoUtils.parseGeoPoint( at org.elasticsearch.index.mapper.geo.GeoPointFieldMapper.parse( at org.elasticsearch.index.mapper.object.ObjectMapper.serializeObject( at org.elasticsearch.index.mapper.object.ObjectMapper.parse( at org.elasticsearch.index.mapper.DocumentMapper.parse( ... 9 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 1 year ago