Include in all is not allowed for indices created on or after version 6.0.0 as – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-6.8

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when you’re trying to use the “include_in_all” parameter in Elasticsearch version 6.0.0 or later. This parameter was deprecated and removed in these versions. To resolve this issue, you can either downgrade to a version that supports “include_in_all” or use the “copy_to” parameter to copy the values of multiple fields into a group field, which can then be searched. Alternatively, you can use a custom “all” field that includes the fields you want to search.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” [include_in_all] is not allowed for indices created on or after version 6.0.0 as ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, version, indices.

Log Context

Log “[include_in_all] is not allowed for indices created on or after version 6.0.0 as” class name is TypeParsers.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (propName.equals("include_in_all")) {
 if (parserContext.isWithinMultiField()) {
 throw new MapperParsingException("include_in_all in multi fields is not allowed. Found the include_in_all in field ["
 + name + "] which is within a multi field.");
 } else if (parserContext.indexVersionCreated().onOrAfter(Version.V_6_0_0_alpha1)) {
 throw new MapperParsingException("[include_in_all] is not allowed for indices created on or after version 6.0.0 as " +
 "[_all] is deprecated. As a replacement; you can use an [copy_to] on mapping fields to create your " +
 "own catch all field.");
 } else {
 builder.includeInAll(nodeBooleanValue(name; "include_in_all"; propNode; parserContext));
 }

 

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?