_na query malformed; must start with start_object – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” _na query malformed; must start with start_object ” to appear. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “[_na] query malformed; must start with start_object”classname  is AbstractQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

* Parses a query excluding the query element that wraps it
 */
 public static QueryBuilder parseInnerQueryBuilder(XContentParser parser) throws IOException {
 if (parser.currentToken() != XContentParser.Token.START_OBJECT) {
 if (parser.nextToken() != XContentParser.Token.START_OBJECT) {
 throw new ParsingException(parser.getTokenLocation(); "[_na] query malformed; must start with start_object");
 }
 }
 if (parser.nextToken() == XContentParser.Token.END_OBJECT) {
 // we encountered '{}' for a query clause; it used to be supported; deprecated in 5.0 and removed in 6.0
 throw new IllegalArgumentException("query malformed; empty clause found at [" + parser.getTokenLocation() +"]");

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content