Failed to parse query. – How to solve this Elasticsearch error

Average Read Time

2 Mins

Failed to parse query. – 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 Error 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 query. ” 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: query and index.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

} else if (token == XContentParser.Token.START_OBJECT) {
  try {
  bbox = GeoBoundingBox.parseBoundingBox(parser);
  fieldName = currentFieldName;
  } catch (Exception e) {
  throw new ElasticsearchParseException("failed to parse [{}] query. [{}]"; NAME; e.getMessage());
  } else if (token.isValue()) {
  if (AbstractQueryBuilder.NAME_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
  queryName = parser.text();
  } else if (AbstractQueryBuilder.BOOST_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {


Run the Check-Up to get a customized report like this:

Analyze your cluster