Failed to parse WKT bounding box. – Elasticsearch Error How To Solve Related Issues



Failed to parse WKT bounding box. – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

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

 

This guide will help you check for common problems that cause the log “failed to parse WKT bounding box.” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: .


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Unloading a ByteArray using Actionscript 3 -views 9,909 

QueryParsingException with a geo bounding box query on a non-existant field ¬∑  



Find Configuration Errors

Analyze Now