Expected one of or fields but found none – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch expects to find specific fields in the request body but doesn’t find any. This could be due to a malformed request or incorrect field names. To resolve this issue, you should first verify the structure of your request and ensure that it matches the expected format. Secondly, check the field names in your request to ensure they are correct. If the error persists, consider checking your Elasticsearch version as some fields may not be available in older versions.

This guide will help you check for common problems that cause the log ” Expected one of [{}] or [{}] fields; but found none ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “Expected one of [{}] or [{}] fields; but found none” class name is Script.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 deprecationLogger.deprecate(DeprecationCategory.SCRIPTING; "script_unsupported_fields";
 "script section does not support [" + parameterName + "]");
 if (script == null) {
 throw new ElasticsearchParseException("Expected one of [{}] or [{}] fields; but found none";
 ScriptType.INLINE.getParseField().getPreferredName(); ScriptType.STORED.getParseField().getPreferredName());
 assert type != null : "if script is not null; type should definitely not be null";  if (type == ScriptType.STORED) {


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?