Registry miss-match – expected SignificantTermsAggregatorSupplier; found – 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 ” Registry miss-match – expected SignificantTermsAggregatorSupplier; found ” 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 “Registry miss-match – expected SignificantTermsAggregatorSupplier; found [“classname  is SignificantTermsAggregatorFactory.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

boolean collectsFromSingleBucket;
 Map metadata) throws IOException {
 AggregatorSupplier aggregatorSupplier = queryShardContext.getValuesSourceRegistry().getAggregator(config;
 SignificantTermsAggregationBuilder.NAME);
 if (aggregatorSupplier instanceof SignificantTermsAggregatorSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected SignificantTermsAggregatorSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 }
 SignificantTermsAggregatorSupplier sigTermsAggregatorSupplier = (SignificantTermsAggregatorSupplier) aggregatorSupplier; 
 BucketCountThresholds bucketCountThresholds = new BucketCountThresholds(this.bucketCountThresholds);

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content