+ NAME + analyzer ” + analyzer + ” not found – Elasticsearch Error How To Solve Related Issues

+ NAME + analyzer ” + analyzer + ” not found – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log ” + NAME + analyzer ” + analyzer + ” not found” 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: query, 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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”[” + NAME + “] analyzer [” + analyzer + “] not found”classname  is MatchBoolPrefixQueryBuilder.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

  protected Query doToQuery(QueryShardContext context) throws IOException {
  if (analyzer != null && context.getIndexAnalyzers().get(analyzer) == null) {
  throw new QueryShardException(context; "[" + NAME + "] analyzer [" + analyzer + "] not found");
  final MatchQuery matchQuery = new MatchQuery(context);
  if (analyzer != null) {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 analyzer not found when creating index mapping -views 5,335 ,score 2

Analyzer not found exception while creating an index with mapping and settings -views   3,886,score 2

Find Configuration Errors

Analyze Now