No time unit specified; did you mean s as in s? – Elasticsearch Error How To Solve Related Issues



No time unit specified; did you mean s as in s? – 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 “No time unit specified; did you mean s as in s?” 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: parser, 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”No time unit specified; did you mean [s] as in [{}s]?”classname  is LogicalPlanBuilder.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
  
  String timeString = text(ctx.timeUnit().IDENTIFIER());
  
  if (timeString == null) {
  throw new ParsingException(source(ctx.timeUnit()); "No time unit specified; did you mean [s] as in [{}s]?"; text(ctx
  .timeUnit()));
  }
  
  TimeUnit timeUnit = null;
  switch (timeString) {

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 Connection Timeout with Elasticsearch -views 77,354 ,score 74

Elasticsearch Scroll -views   25,562,score 11



Find Configuration Errors

Analyze Now