Unsupported script value o expected a number date or boolean – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch encounters a script value that is not a number, date, or boolean. This could be due to incorrect data types being used in the script. To resolve this issue, you should first check the script and ensure that the values being used are of the correct data type. If they are not, you should convert them to the appropriate type. Additionally, ensure that the script is correctly formatted and does not contain any syntax errors.

This guide will help you check for common problems that cause the log ” Unsupported script value [” + o + “]; expected a number; date; or boolean ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, aggregations.

Log Context

Log “Unsupported script value [” + o + “]; expected a number; date; or boolean” class name is ScriptDoubleValues.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // that scripts return the same internal representation as regular fields; so boolean
 // values in scripts need to be converted to a number; and the value formatter will
 // make sure of using true/false in the key_as_string field
 return ((Boolean) o).booleanValue() ? 1.0 : 0.0;
 } else {
 throw new AggregationExecutionException("Unsupported script value [" + o + "]; expected a number; date; or boolean");
 }  @Override
 public void setScorer(Scorable scorer) {


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?