NAME no mapping found for type type – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch cannot find a mapping for a specific field type in the index. This could be due to a typo in the field type or the mapping was not properly defined. To resolve this issue, you can check the field type for any spelling errors or inconsistencies. If the mapping was not defined, you need to define it using the “PUT mapping” API. Also, ensure that the field type you’re trying to map is supported by Elasticsearch.

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

Log Context

Log “[” + NAME + “] no mapping found for type [” + type + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 DocumentMapper childDocMapper = context.getMapperService().documentMapper(type);
 if (childDocMapper == null) {
 if (ignoreUnmapped) {
 return new MatchNoDocsQuery();
 } else {
 throw new QueryShardException(context; "[" + NAME + "] no mapping found for type [" + type + "]");
 ParentFieldMapper parentFieldMapper = childDocMapper.parentFieldMapper();
 if ( == false) {
 throw new QueryShardException(context; "[" + NAME + "] _parent field has no parent type configured");