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.
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.
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
Find & fix Elasticsearch problems
