Expected FIELD_NAME but got ” + parser.currentToken() + ” – How to solve this Elasticsearch error

Expected FIELD_NAME but got ” + parser.currentToken() + ” – 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 ” Expected FIELD_NAME but got ” + parser.currentToken() + ” ” 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: parser, 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”Expected [FIELD_NAME] but got [” + parser.currentToken() + “]”classname  is IntervalQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

builder.endObject();
  }
 
  public static IntervalQueryBuilder fromXContent(XContentParser parser) throws IOException {
  if (parser.nextToken() != XContentParser.Token.FIELD_NAME) {
  throw new ParsingException(parser.getTokenLocation(); "Expected [FIELD_NAME] but got [" + parser.currentToken() + "]");
  }
  String field = parser.currentName();
  if (parser.nextToken() != XContentParser.Token.START_OBJECT) {
  throw new ParsingException(parser.getTokenLocation(); "Expected [START_OBJECT] but got [" + parser.currentToken() + "]");
  }

 

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

Analyze your cluster