Failed to find type parsed ” + mappingType + ” for ” + name + ” – 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 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 ” failed to find type parsed ” + mappingType + ” for ” + name + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: mapping and index.

Log Context

Log “failed to find type parsed [” + mappingType + “] for [” + name + “]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 Mapper.TypeParser.ParserContext parserContext = context.docMapperParser().parserContext();
 String mappingType = dynamicTemplate.mappingType(dynamicType);
 Mapper.TypeParser typeParser = parserContext.typeParser(mappingType);
 if (typeParser == null) {
 throw new MapperParsingException("failed to find type parsed [" + mappingType + "] for [" + name + "]");
 return typeParser.parse(name; dynamicTemplate.mappingForName(name; dynamicType); parserContext);
 public DynamicTemplate findTemplate(ContentPath path; String name; XContentFieldType matchType) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content