+ NAME + no relation found for child ” + type + ” – How to solve this Elasticsearch error

Average Read Time

2 Mins

+ NAME + no relation found for child ” + type + ” – 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 Check-Up which can resolve issues that cause many errors.

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

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “[” + NAME + “] no relation found for child [” + type + “]”classname  is ParentIdQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final ParentIdFieldMapper childMapper = joinFieldMapper.getParentIdFieldMapper(type; false);
 if (childMapper == null) {
 if (ignoreUnmapped) {
 return new MatchNoDocsQuery();
 } else {
 throw new QueryShardException(context; "[" + NAME + "] no relation found for child [" + type + "]");
 }
 }
 return new BooleanQuery.Builder()
 .add(childMapper.fieldType().termQuery(id; context); BooleanClause.Occur.MUST)
 // Need to take child type into account; otherwise a child doc of different type with the same id could match

 

Watch a demo of the Check-Up:

Analyze your cluster