Expected one of or fields; but found none – 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.

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 ” 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: reindex and index.

Log Context

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

throw new ElasticsearchParseException("Value must be of type String: [" + 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) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content