Percolator fields are not searchable directly; use a percolate query instead

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 ” Percolator fields are not searchable directly; use a percolate query instead ” 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: percolate, percolator and query.

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”Percolator fields are not searchable directly; use a percolate query instead”classname is PercolatorFieldMapper.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
  }
 
  @Override
  public Query termQuery(Object value; QueryShardContext context) {
  throw new QueryShardException(context; "Percolator fields are not searchable directly; use a percolate query instead");
  }
 
  Query percolateQuery(String name; PercolateQuery.QueryStore queryStore; List documents;
  IndexSearcher searcher; boolean excludeNestedDocuments; Version indexVersion) throws IOException {
  IndexReader indexReader = searcher.getIndexReader();