Expected END 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 encounters a syntax error in the JSON input. It’s expecting the end of an object (a closing curly brace “}”) but is finding a different token instead. This could be due to a missing or misplaced comma, bracket, or brace in the JSON. To resolve this issue, carefully review the JSON input for any syntax errors. Use a JSON validator tool to help identify and correct these errors. Also, ensure that all objects, arrays, and other elements are properly closed with the correct punctuation.

This guide will help you check for common problems that cause the log ” Expected [END_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 [END_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 :

 provider = IntervalsSourceProvider.fromXContent(parser);
 if (parser.nextToken() != XContentParser.Token.END_OBJECT) {
 throw new ParsingException(parser.getTokenLocation(); "Expected [END_OBJECT] but got [" + parser.currentToken() + "]");
 if (provider == null) {
 throw new ParsingException(parser.getTokenLocation(); "Missing intervals from interval query definition");
 IntervalQueryBuilder builder = new IntervalQueryBuilder(field; provider);


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?