Analyzer ” + name + ” contains filters – How to solve this Elasticsearch error

Analyzer ” + name + ” contains filters – 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 ” analyzer ” + name + ” contains filters ” 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: analysis and index.

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”analyzer [” + name + “] contains filters”classname  is NamedAnalyzer.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

for (TokenFilterFactory tokenFilter : tokenFilters) {
  if (tokenFilter.getAnalysisMode() != mode) {
  offendingFilters.add(tokenFilter.name());
  }
  }
  throw new MapperException("analyzer [" + name + "] contains filters " + offendingFilters
  + " that are not allowed to run in " + mode.getReadableName() + " mode.");
  } else {
  throw new MapperException(
  "analyzer [" + name + "] contains components that are not allowed to run in " + mode.getReadableName() + " mode.");
  }

 

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

Analyze your cluster