No parameter named and type OBJECT – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch encounters a request with an unrecognized parameter. This could be due to a typo in the parameter name, or the parameter might not be applicable to the specific Elasticsearch operation being performed. To resolve this issue, you should first verify the parameter name and its spelling. If the name is correct, check the Elasticsearch documentation to ensure the parameter is valid for the operation you’re trying to perform. If the parameter is not applicable, remove it from the request.

This guide will help you check for common problems that cause the log ” no parameter named [{}] and type OBJECT ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “no parameter named [{}] and type OBJECT” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (token == XContentParser.Token.START_OBJECT && currentFieldName != null) {
 if ("parameters".equals(currentFieldName)) {
 TermVectorsRequest.parseRequest(template; parser; parser.getRestApiVersion());
 } else {
 throw new ElasticsearchParseException("no parameter named [{}] and type OBJECT"; currentFieldName);
 } else if (currentFieldName != null) {
 throw new ElasticsearchParseException("_mtermvectors: Parameter [{}] not supported"; currentFieldName);


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?