Cannot parse empty date – Elasticsearch Error How To Solve Related Issues

Cannot parse empty date – 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 “cannot parse empty date” 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: .

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”cannot parse empty date”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return dateTime.toInstant();
  private Instant parseDateTime(String value; ZoneId timeZone; boolean roundUpIfNoTime) {
  if (Strings.isNullOrEmpty(value)) {
  throw new ElasticsearchParseException("cannot parse empty date");
  DateFormatter formatter = roundUpIfNoTime ? this.roundupParser : this.formatter;
  try {
  if (timeZone == 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 Empty string in Elasticsearch date field? -views 17,750 ,score 8

Elastic Search: indexing dates field that has null values -views   1,733

Find Configuration Errors

Analyze Now