Array elements in include/exclude clauses should be string values – 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 ” Array elements in include/exclude clauses should be string values ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search and aggregations.

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 “Array elements in include/exclude clauses should be string values”classname  is IncludeExclude.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (parser.currentToken() != XContentParser.Token.START_ARRAY) {
 throw new ElasticsearchParseException("Missing start of array in include/exclude clause");
 }
 while (parser.nextToken() != XContentParser.Token.END_ARRAY) {
 if (!parser.currentToken().isValue()) {
 throw new ElasticsearchParseException("Array elements in include/exclude clauses should be string values");
 }
 set.add(new BytesRef(parser.text()));
 }
 return set;
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content