Briefly, this error occurs when Elasticsearch is unable to parse the time because the minute value provided is not a number. This could be due to incorrect data type or format. To resolve this issue, ensure that the time value is correctly formatted and the minute value is a numerical value. Also, check your mapping and ensure that the field is correctly mapped as a date type. If you’re using a script or application to input data, verify that it’s correctly formatting the time values.
This guide will help you check for common problems that cause the log ” could not parse time [{}]. time minute [{}] 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 minute [{}] 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 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);
}
try {
return new DayTimes(time; hour; minute);
} catch (IllegalArgumentException iae) {
throw new ElasticsearchParseException("could not parse time [{}]"; iae);
[ratemypost]