Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
Take a self-guided product tour to see for yourself (no registration required).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.
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();
