Failed to parse WKT bounding box. – How to solve this Elasticsearch error

Average Read Time

2 Mins

Failed to parse WKT bounding box. – 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 ” failed to parse WKT bounding box. ” 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 “failed to parse WKT bounding box. [“classname  is GeoBoundingBox.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

token = parser.nextToken();
 if (WKT_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 try {
 Geometry geometry = WKT_PARSER.fromWKT(parser.text());
 if (ShapeType.ENVELOPE.equals(geometry.type()) == false) {
 throw new ElasticsearchParseException("failed to parse WKT bounding box. ["
 + geometry.type() + "] found. expected [" + ShapeType.ENVELOPE + "]");
 }
 envelope = (Rectangle) geometry;
 } catch (ParseException|IllegalArgumentException e) {
 throw new ElasticsearchParseException("failed to parse WKT bounding box"; e);

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content