Could not parse date/time. expected date field to be either a number or a – Elasticsearch Error How To Solve Related Issues



Could not parse date/time. expected date field to be either a number or a – 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 “could not parse date/time. expected date field to be either a number or a” 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”could not parse date/time. expected date field [{}] to be either a number or a”classname  is WatcherDateTimeUtils.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
  if (token == XContentParser.Token.VALUE_STRING) {
  try {
  return parseDateMath(parser.text(); timeZone; clock);
  } catch (ElasticsearchParseException epe) {
  throw new ElasticsearchParseException("could not parse date/time. expected date field [{}] to be either a number or a " +
  "DateMath string but found [{}] instead"; epe; fieldName; parser.text());
  }
  }
  if (token == XContentParser.Token.VALUE_NULL) {
  return null;

 

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 Illegal pattern character 'T' when parsing a date string to java.util.Date -views 127,645 ,score 181

JSON parse error: Can not construct instance of java.time.LocalDate: no String-argument constructor/factory method to deserialize from String value -views   72,891,score 42

 

 

About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now