No time unit specified; did you mean s as in s? – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause 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. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content