Registry miss-match – expected SignificantTermsAggregatorSupplier found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.8-7.9

Briefly, this error occurs when there’s a mismatch between the expected and found aggregator in Elasticsearch. This usually happens when you’re trying to use an aggregation that doesn’t match with the field type in your index. To resolve this issue, you can either change the field type in your index to match the expected aggregator or use an appropriate aggregation that matches with the current field type in your index. Also, ensure that your Elasticsearch version supports the aggregation you’re trying to use.

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, aggregations.

Log Context

Log “Registry miss-match – expected SignificantTermsAggregatorSupplier; found [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 CardinalityUpperBound cardinality;
 Map metadata) throws IOException {
 AggregatorSupplier aggregatorSupplier = queryShardContext.getValuesSourceRegistry().getAggregator(config;
 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);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?