Parameter not supported! – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error suggests that the parameter used in the Elasticsearch query is not supported by the version of Elasticsearch being used. Elasticsearch parameters can change between different versions, and an unsupported parameter can cause the query to fail. To resolve this error, check the Elasticsearch documentation for the correct version and ensure that the parameters used in the query are supported.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” parameter not supported! ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query and index.

Log Context

Log “parameter [{}] not supported!”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

origin = parser.doubleValue();
 refFound = true;
 } else if (DecayFunctionBuilder.OFFSET.equals(parameterName)) {
 offset = parser.doubleValue();
 } else {
 throw new ElasticsearchParseException("parameter [{}] not supported!"; parameterName);
 if (!scaleFound || !refFound) {
 throw new ElasticsearchParseException("both [{}] and [{}] must be set for numeric fields."; DecayFunctionBuilder.SCALE;


See how you can use AutoOps to resolve issues

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?

Analyze your cluster & get personalized recommendations

Skip to content