Expected field – How to solve this Elasticsearch error

Average Read Time

2 Mins

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 Error 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. 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: percolator.

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”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;


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

Analyze your cluster