Aggregation ” + parent.name() + ” cannot have a global ” + “sub-aggregation – How to solve this Elasticsearch error

Average Read Time

2 Mins

Aggregation ” + parent.name() + ” cannot have a global ” + “sub-aggregation – 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 ” Aggregation ” + parent.name() + ” cannot have a global ” + “sub-aggregation ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search and aggregations.

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 “Aggregation [” + parent.name() + “] cannot have a global ” + “sub-aggregation [“classname  is GlobalAggregatorFactory.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public Aggregator createInternal(SearchContext searchContext;
 Aggregator parent;
 boolean collectsFromSingleBucket;
 Map metadata) throws IOException {
 if (parent != null) {
 throw new AggregationExecutionException("Aggregation [" + parent.name() + "] cannot have a global " + "sub-aggregation [" + name
 + "]. Global aggregations can only be defined as top level aggregations");
 }
 if (collectsFromSingleBucket == false) {
 throw new IllegalStateException();
 }

 

Watch a demo of the Check-Up:

Analyze your cluster