Invalid year month value. expected a string or a number value; but found – Elasticsearch Error How To Solve Related Issues



Invalid year month value. expected a string or a number value; but found – 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 month value. expected a string or a number value; but found” 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 month value. expected a string or a number value; but found [{}]”classname  is YearTimes.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return Month.resolve(parser.text());
  }
  if (token == XContentParser.Token.VALUE_NUMBER) {
  return Month.resolve(parser.intValue());
  }
  throw new ElasticsearchParseException("invalid year month value. expected a string or a number value; but found [{}]"; token);
  }
 
  public static class Builder {
 
  private final Set months = new HashSet();







Find Configuration Errors

Try The Tool