Briefly, this error occurs when Elasticsearch encounters an invalid minute value in a time field. It expects a string or number but found a different data type. This could be due to incorrect data input or a mismatch in the expected data type. To resolve this, ensure that the minute value is a string or number. Check your data input or mapping to ensure it matches the expected data type. If you’re using a script or application to input data, ensure it’s correctly formatted before sending to Elasticsearch.
This guide will help you check for common problems that cause the log ” invalid time minute value. expected string/number value; but found [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “invalid time minute value. expected string/number value; but found [{}]” class name is DayTimes.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} catch (NumberFormatException nfe) {
throw new ElasticsearchParseException("invalid time minute value [{}]"; value);
} default:
throw new ElasticsearchParseException("invalid time minute value. expected string/number value; but found [{}]"; token);
}
} }
