Invalid hour value. expected string/number value; but found – Elasticsearch Error How To Solve Related Issues



Invalid hour value. expected string/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 hour value. expected string/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 hour value. expected string/number value; but found [{}]”classname  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 hour value [{}]"; value);
  }
 
  default:
  throw new ElasticsearchParseException("invalid hour value. expected string/number value; but found [{}]"; token);
  }
  }
 
  public static int parseMinuteValue(XContentParser parser; XContentParser.Token token) throws IOException; ElasticsearchParseException {
  switch (token) {

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 Warning: A non-numeric value encountered -views 323,634 ,score 116

Expected block end YAML error -views   117,555,score 26



Find Configuration Errors

Analyze Now