Stored_fields cannot be disabled when using the fields option – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” stored_fields cannot be disabled when using the fields option ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “[stored_fields] cannot be disabled when using the [fields] option”classname  is SearchService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (source.storedFields().fetchFields() == false) {
 if (context.sourceRequested()) {
 throw new SearchException(shardTarget; "[stored_fields] cannot be disabled if [_source] is requested");
 }
 if (context.fetchFieldsContext() != null) {
 throw new SearchException(shardTarget; "[stored_fields] cannot be disabled when using the [fields] option");
 }
 }
 context.storedFieldsContext(source.storedFields());
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content