Invalid year day value for field. expected string/number value or an – Elasticsearch Error How To Solve Related Issues



Invalid year day value for field. expected string/number value or an – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 

 

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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”invalid year day value for [{}] field. expected string/number value or an”classname  is YearTimes.java
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 {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 ValueError: invalid literal for int () with base 10 -views 468,453 ,score 72

SyntaxError invalid token -views   79,784,score 41



Find Configuration Errors

Analyze Now