Expected START OBJECT but got parser currentToken – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-8.9

Briefly, this error occurs when Elasticsearch expects a JSON object to start (START_OBJECT) but encounters a different type of data. This is usually due to incorrect or malformed JSON input. To resolve this issue, you can: 1) Check the JSON input for syntax errors or misplaced commas, brackets, or braces. 2) Validate your JSON input using a JSON validator tool. 3) Ensure that the JSON input matches the expected structure for the Elasticsearch API you’re using.

This guide will help you check for common problems that cause the log ” Expected [START_OBJECT] but got [” + parser.currentToken() + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser, query, index.

Log Context

Log “Expected [START_OBJECT] but got [” + parser.currentToken() + “]” class name is IntervalQueryBuilder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 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() + "]");
 String name = null;
 float boost = 1;
 IntervalsSourceProvider provider = null;
 String providerName = null;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?