Wrapper query malformed; expected `query` but was – 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 ” wrapper query malformed; expected `query` but was ” 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 “[wrapper] query malformed; expected `query` but was”classname  is WrapperQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (token != XContentParser.Token.FIELD_NAME) {
 throw new ParsingException(parser.getTokenLocation(); "[wrapper] query malformed");
 }
 String fieldName = parser.currentName();
 if (! QUERY_FIELD.match(fieldName; parser.getDeprecationHandler())) {
 throw new ParsingException(parser.getTokenLocation(); "[wrapper] query malformed; expected `query` but was " + fieldName);
 }
 parser.nextToken(); 
 byte[] source = parser.binaryValue();

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content