Registry miss-match – expected TermsAggregatorSupplier 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 due to version incompatibility or incorrect usage of aggregations. To resolve this issue, ensure that you’re using the correct version of Elasticsearch that supports the aggregations you’re using. Also, check your aggregation queries to ensure they’re correctly formed. If the problem persists, consider updating or downgrading your Elasticsearch version to match the requirements of your aggregations.

This guide will help you check for common problems that cause the log ” Registry miss-match – expected TermsAggregatorSupplier; 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 TermsAggregatorSupplier; 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 TermsAggregatorSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected TermsAggregatorSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 }  TermsAggregatorSupplier termsAggregatorSupplier = (TermsAggregatorSupplier) aggregatorSupplier;
 BucketCountThresholds bucketCountThresholds = new BucketCountThresholds(this.bucketCountThresholds);