Decimal time interval not supported please use an positive integer – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.8-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when a decimal value is used for a time interval in Elasticsearch, which only supports positive integers. To resolve this issue, you should ensure that all time intervals are specified as positive integers. If you’re using a script or application to generate these values, you may need to adjust it to round to the nearest whole number or to avoid generating decimal values.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Decimal time interval [{}] not supported; please use an positive integer ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, parser.

Log Context

Log “Decimal time interval [{}] not supported; please use an positive integer” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  return new TimeValue(value; timeUnit);  } else {
 throw new ParsingException(source(numberCtx); "Decimal time interval [{}] not supported; please use an positive integer";
 }  private LogicalPlan pipe(PipeContext ctx; LogicalPlan plan) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?