Setting index 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Setting index 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.

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 “Setting [index] 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 :

// 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 + "]");
 } 
 TypeParsers.parseField(builder; name; node; parserContext); 
 return builder;

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content