Opster Team
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.
Take a self-guided product tour to see for yourself (no registration required).This guide will help you check for common problems that cause the log ” has_child query does not support ” + currentFieldName + ” ” 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 “[has_child] query does not support [” + currentFieldName + “]”classname is HasChildQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (QUERY_FIELD.match(currentFieldName; parser.getDeprecationHandler())) { iqb = parseInnerQueryBuilder(parser); } else if (INNER_HITS_FIELD.match(currentFieldName; parser.getDeprecationHandler())) { innerHitBuilder = InnerHitBuilder.fromXContent(parser); } else { throw new ParsingException(parser.getTokenLocation(); "[has_child] query does not support [" + currentFieldName + "]"); } } else if (token.isValue()) { if (TYPE_FIELD.match(currentFieldName; parser.getDeprecationHandler())) { childType = parser.text(); } else if (SCORE_MODE_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 2 minutes
Lourens Rozema
CTO at Omnidots