Setting doc_values cannot be modified for field ” + name + ” – 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 ” Setting doc_values cannot be modified for field ” + name + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins and index.


Log Context

Log “Setting [doc_values] cannot be modified for field [” + name + “]”classname  is Murmur3FieldMapper.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throws MapperParsingException {
 Builder builder = new Builder(name); 
 // tweaking these settings is no longer allowed; the entire purpose of murmur3 fields is to store a hash
 if (node.get("doc_values") != null) {
 throw new MapperParsingException("Setting [doc_values] cannot be modified for field [" + name + "]");
 }
 if (node.get("index") != null) {
 throw new MapperParsingException("Setting [index] cannot be modified for field [" + name + "]");
 }

 

See how you can use AutoOps to resolve issues


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?

Analyze your cluster & get personalized recommendations

Skip to content