Invalid year day value for field expected string number value or an – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when the year day value provided in the Elasticsearch query is invalid. This could be due to incorrect data type or format. Elasticsearch expects a string or number value for the year day field. To resolve this issue, ensure that the year day value is correctly formatted and of the right data type. Also, check your query syntax to ensure it’s correct. If the error persists, consider re-indexing your data to ensure all date fields are correctly mapped.

This guide will help you check for common problems that cause the log ” invalid year day value for [{}] field. expected string/number value or an ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “invalid year day value for [{}] field. expected string/number value or an” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (token == XContentParser.Token.START_ARRAY) {
 while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
 daysSet.add(MonthTimes.parseDayValue(parser; token));
 } else {
 throw new ElasticsearchParseException("invalid year day value for [{}] field. expected string/number value or an " +
 "array of string/number values; but found [{}]"; currentFieldName; token);
 } else if (TIME_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token != XContentParser.Token.START_ARRAY) {
 try {


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?