Registry miss-match – expected DateHistogramAggregationSupplier; 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 DateHistogramAggregationSupplier; 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 DateHistogramAggregationSupplier; found [“classname  is DateHistogramAggregatorFactory.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;
 DateHistogramAggregationBuilder.NAME);
 if (aggregatorSupplier instanceof DateHistogramAggregationSupplier == false) {
 throw new AggregationExecutionException("Registry miss-match - expected DateHistogramAggregationSupplier; found [" +
 aggregatorSupplier.getClass().toString() + "]");
 }
 // TODO: Is there a reason not to get the prepared rounding in the supplier itself?
 Rounding.Prepared preparedRounding = config.getValuesSource()
 .roundingPreparer(queryShardContext.getIndexReader())

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content