Expected geometry type but found – How to solve this Elasticsearch error

Average Read Time

2 Mins

Expected geometry type but found – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Expected geometry type but found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Expected geometry type [{}] but found [{}]”classname  is GeoWKTParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final boolean coerce)
 throws IOException; ElasticsearchParseException {
 final GeoShapeType type = GeoShapeType.forName(nextWord(stream));
 if (shapeType != null && shapeType != GeoShapeType.GEOMETRYCOLLECTION) {
 if (type.wktName().equals(shapeType.wktName()) == false) {
 throw new ElasticsearchParseException("Expected geometry type [{}] but found [{}]"; shapeType; type);
 }
 }
 switch (type) {
 case POINT:
 return parsePoint(stream; ignoreZValue; coerce);

 

Watch a demo of the Check-Up:

Analyze your cluster