Common analyzer analyzer not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

Briefly, this error occurs when Elasticsearch tries to use an analyzer that doesn’t exist in its configuration. An analyzer is a component that breaks down text into tokens for indexing. The error indicates that the specified analyzer is not found in the Elasticsearch settings. To resolve this issue, you can either create a new custom analyzer with the specified name or change your request to use one of the built-in analyzers. Also, ensure that the analyzer is correctly defined in your index settings.

This guide will help you check for common problems that cause the log ” [common] analyzer [” + analyzer + “] not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, query.

Log Context

Log “[common] analyzer [” + analyzer + “] not found” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (analyzer == null) {
 analyzerObj = fieldType.getTextSearchInfo().getSearchAnalyzer();
 } else {
 analyzerObj = context.getIndexAnalyzers().get(analyzer);
 if (analyzerObj == null) {
 throw new QueryShardException(context; "[common] analyzer [" + analyzer + "] not found");
 }  Occur highFreqOccur = highFreqOperator.toBooleanClauseOccur();
 Occur lowFreqOccur = lowFreqOperator.toBooleanClauseOccur();