QueryName query malformed no start object after query name – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch receives a query that is not properly formatted. Specifically, it expects a start_object (usually denoted by ‘{‘) after the query name, but it’s not finding one. This could be due to a syntax error or a missing bracket. To resolve this issue, you should review the query to ensure it’s correctly structured. Make sure that each query name is followed by a ‘{‘ and ended with a ‘}’. Also, ensure that all brackets are properly paired and nested.

This guide will help you check for common problems that cause the log ” [” + queryName + “] query malformed; no start_object after query name ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query, index.

Log Context

Log “[” + queryName + “] query malformed; no start_object after query name” class name is AbstractQueryBuilder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new ParsingException(parser.getTokenLocation(); "[_na] query malformed; no field after start_object");
 String queryName = parser.currentName();
 // move to the next START_OBJECT
 if (parser.nextToken() != XContentParser.Token.START_OBJECT) {
 throw new ParsingException(parser.getTokenLocation(); "[" + queryName + "] query malformed; no start_object after query name");
 QueryBuilder result;
 try {
 result = parser.namedObject(QueryBuilder.class; queryName; null);
 } catch (NamedObjectNotFoundException e) {


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?