Cannot determine datatype for combination – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to determine the data type for a specific field or combination of fields. This could be due to incorrect or missing mapping definitions. To resolve this issue, you can explicitly define the mapping for the field in question, specifying the correct data type. Alternatively, you can reindex your data, ensuring that the data types are correctly inferred during the indexing process. Lastly, check your data for inconsistencies or anomalies that might be causing the data type confusion.

This guide will help you check for common problems that cause the log ” Cannot determine datatype for combination [{}] [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Cannot determine datatype for combination [{}] [{}]” class name is Intervals.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return INTERVAL_HOUR_TO_SECOND;
 }
 if (leading == TimeUnit.MINUTE && trailing == TimeUnit.SECOND) {
 return INTERVAL_MINUTE_TO_SECOND;
 }
 throw new ParsingException(source; "Cannot determine datatype for combination [{}] [{}]"; leading; trailing);
 }
 }  // return the compatible interval between the two - it is assumed the types are intervals
 // YEAR and MONTH -> YEAR_TO_MONTH

 

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?