Parameter not supported – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when you’re trying to use a parameter in Elasticsearch that it doesn’t recognize or support. This could be due to a typo, using a deprecated parameter, or using a parameter that doesn’t exist in the current version of Elasticsearch. To resolve this issue, you should first check for typos in your parameter name. If there are none, verify that the parameter is not deprecated or removed in the Elasticsearch version you’re using. If it’s a custom parameter, ensure it’s correctly implemented in your Elasticsearch configuration.

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, index.

Log Context

Log “parameter [{}] not supported!” class name 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 == false || refFound == false) {
 throw new ElasticsearchParseException(
 "both [{}] and [{}] must be set for numeric fields.";


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?