Updated: July-20
Elasticsearch Version: 1.7-8.0
Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues causing many errors
This guide will help you check for common problems that cause the log ” + NAME + no relation found for child ” + type + “” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: join, query.
Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation).
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
Related issues to this log
We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :
1 Parent/Child relationships in spring-data-elastic-search -views 9,061 ,score 4
2 Having trouble creating Parent-Child Relationship in ElasticSearch 6 -views 4,304,score 4
About Opster
Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch
