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

Opster Team

August-23, Version: 7.8-7.8

Briefly, this error occurs when there’s a mismatch between the expected and actual data type in Elasticsearch. Specifically, the system expected a DateHistogramAggregationSupplier but found a different type. This could be due to incorrect data mapping or a bug in the code. To resolve this issue, you can check and correct your data mapping, ensure that the correct data type is being used, or debug your code to identify and fix any potential bugs.

This guide will help you check for common problems that cause the log ” Registry miss-match – expected DateHistogramAggregationSupplier; 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 DateHistogramAggregationSupplier; found [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return asMultiBucketAggregator(this; searchContext; parent);
 AggregatorSupplier aggregatorSupplier = queryShardContext.getValuesSourceRegistry().getAggregator(config.valueSourceType();
 if (aggregatorSupplier instanceof DateHistogramAggregationSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected DateHistogramAggregationSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 return ((DateHistogramAggregationSupplier) aggregatorSupplier).build(name; factories; rounding; shardRounding; order; keyed;
 minDocCount; extendedBounds; valuesSource; config.format(); searchContext; parent; metadata);