NAME parent field has no parent type configured – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-6.8

Briefly, this error occurs when the “_parent” field in an Elasticsearch document is not properly configured with a parent type. This is a requirement for parent-child relationships in Elasticsearch. To resolve this issue, you can either configure a parent type for the “_parent” field or remove the “_parent” field if it’s not necessary. Also, ensure that the parent type exists in your index mapping. If you’re using Elasticsearch 6.x or later, consider using the “join” field instead, as parent-child relationships are deprecated.

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

Log Context

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

 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");
 String parentType = parentFieldMapper.type();
 DocumentMapper parentDocMapper = context.getMapperService().documentMapper(parentType);
 if (parentDocMapper == null) {
 throw new QueryShardException(context;