No data provided for multipoint object when expecting – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is expecting data for a multipoint object, but none is provided. This usually happens when you’re trying to index a document with a geo_shape field, but the coordinates for the multipoint object are missing or null. To resolve this issue, ensure that the document you’re trying to index contains valid coordinates for the multipoint object. Alternatively, you can set the ignore_malformed option to true in your mapping, which will allow documents to be indexed even if they contain malformed geo_shapes.

This guide will help you check for common problems that cause the log ” no data provided for multipoint object when expecting ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “no data provided for multipoint object when expecting” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (coordinates.children == null || coordinates.children.isEmpty()) {
 if (coordinates.coordinate != null) {
 throw new ElasticsearchParseException("single coordinate found when expecting an array of " +
 "coordinates. change type to point or change data to an array of >0 coordinates");
 throw new ElasticsearchParseException("no data provided for multipoint object when expecting " +
 ">0 points (e.g.; [[lat; lng]] or [[lat; lng]; ...])");
 } else {
 for (CoordinateNode point : coordinates.children) {
 POINT.validate(point; coerce);