Registry miss-match – expected AutoDateHistogramAggregationSupplier 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 aggregation types in Elasticsearch. The system expected AutoDateHistogramAggregationSupplier but found something different. This could be due to incorrect configuration or a bug in the code. To resolve this issue, you can: 1) Check your Elasticsearch configuration and ensure the correct aggregation type is specified. 2) Review your code to ensure the correct aggregation type is being used. 3) Update or reinstall Elasticsearch if the error persists, as it could be due to a bug in the version you’re using.

This guide will help you check for common problems that cause the log ” Registry miss-match – expected AutoDateHistogramAggregationSupplier; 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 AutoDateHistogramAggregationSupplier; 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 AutoDateHistogramAggregatorSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected AutoDateHistogramAggregationSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 Function roundingPreparer =
 return ((AutoDateHistogramAggregatorSupplier) aggregatorSupplier).build(name; factories; numBuckets; roundingInfos;


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?