Briefly, this error occurs when Elasticsearch is unable to parse the time because the hour value is not a number. This could be due to incorrect data format or a typo in the time value. To resolve this issue, ensure that the time value is in the correct format and that the hour value is a number. If the error persists, check your data source for any inconsistencies or errors. Additionally, you may need to update your Elasticsearch mapping to correctly interpret the time field.
This guide will help you check for common problems that cause the log ” could not parse time [{}]. time hour [{}] is not a number ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “could not parse time [{}]. time hour [{}] is not a number” class name is DayTimes.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
throw new ElasticsearchParseException("could not parse time [{}]. time format must be in the form of hh:mm"; time);
}
try {
hour = new int[] { Integer.parseInt(hrStr) };
} catch (NumberFormatException nfe) {
throw new ElasticsearchParseException("could not parse time [{}]. time hour [{}] is not a number"; time; hrStr);
}
try {
minute = new int[] { Integer.parseInt(minStr) };
} catch (NumberFormatException nfe) {
throw new ElasticsearchParseException("could not parse time [{}]. time minute [{}] is not a number"; time; minStr);
