Percolator fields are not searchable directly; use a percolate query instead – How to solve this Elasticsearch error

Average Read Time

2 Mins

Percolator fields are not searchable directly; use a percolate query instead – 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 ” Percolator fields are not searchable directly; use a percolate query instead ” to appear. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

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();

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content