Wrapper query malformed; expected `query` but was – How to solve this Elasticsearch error

Average Read Time

2 Mins

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 Error 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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);
  byte[] source = parser.binaryValue();


Run the Check-Up to get a customized report like this:

Analyze your cluster