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

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

Updated: July-20

Elasticsearch Version: 1.7-8.0

This guide will help you check for common problems that cause the error message”failed to parse bounding box. unexpected field”. To understand what might cause it to appear, read bellow frequent issues related to the Elasticsearch concepts: .

Advanced users might want to skip right to trying out the Elasticsearch Error Check-Up, which analyses ES to discover the cause of many errors to provide actionable recommendations (JSON based, no fee and just 2 minutes to complete).

Log Context

Log”failed to parse bounding box. unexpected field [{}]”classname  is GeoBoundingBox.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else if (BOTTOM_LEFT_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
  GeoUtils.parseGeoPoint(parser; sparse; false; GeoUtils.EffectivePoint.BOTTOM_LEFT);
  bottom = sparse.getLat();
  left = sparse.getLon();
  } else {
  throw new ElasticsearchParseException("failed to parse bounding box. unexpected field [{}]"; currentFieldName);
  }
  }
  } else {
  throw new ElasticsearchParseException("failed to parse bounding box. field name expected but [{}] found"; token);
  }

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 IndexError: tuple index out of range —– Python -views 345,733 ,score 39

JsonMappingException: out of START_ARRAY token -views   306,044,score 101

 

 

About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now