Expected field – 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 ” expected field ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: percolator.

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 “expected field [“classname  is PercolateQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (fieldType == null) {
 throw new QueryShardException(context; "field [" + field + "] does not exist");
 if (!(fieldType instanceof PercolatorFieldMapper.PercolatorFieldType)) {
 throw new QueryShardException(context; "expected field [" + field +
 "] to be of type [percolator]; but is of type [" + fieldType.typeName() + "]");
 final List docs = new ArrayList<>();
 final DocumentMapper docMapper;


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content