Has_child query does not support " + currentFieldName + "

Opster Team

July-20, 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 that cause many errors.

This guide will help you check for common problems that cause the log ” has_child query does not support ” + currentFieldName + ” ” 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 and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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())) {