The `enabled` setting for the `_field_names` field has been deprecated and – 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.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” The `enabled` setting for the `_field_names` field has been deprecated and ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “The `enabled` setting for the `_field_names` field has been deprecated and”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

String fieldName = entry.getKey();
 Object fieldNode = entry.getValue();
 if (fieldName.equals("enabled")) {
 String indexName = parserContext.mapperService().index().getName();
 if (parserContext.indexVersionCreated().onOrAfter(Version.V_8_0_0)) {
 throw new MapperParsingException("The `enabled` setting for the `_field_names` field has been deprecated and "
 + "removed but is still used in index [{}]. Please remove it from your mappings and templates.");
 } else {
 deprecationLogger.deprecate("field_names_enabled_parameter"; ENABLED_DEPRECATION_MESSAGE; indexName);
 builder.enabled(XContentMapValues.nodeBooleanValue(fieldNode; name + ".enabled"));


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content