Source definition may not contain – How to solve this Elasticsearch error

Average Read Time

2 Mins

Source definition may not contain – 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 ” source definition may not contain ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: source.

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 “source definition may not contain [{}]”classname  is MultiGetRequest.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if ("includes".equals(currentFieldName) || "include".equals(currentFieldName)) {
 currentList = includes != null ? includes : (includes = new ArrayList<>(2));
 } else if ("excludes".equals(currentFieldName) || "exclude".equals(currentFieldName)) {
 currentList = excludes != null ? excludes : (excludes = new ArrayList<>(2));
 } else {
 throw new ElasticsearchParseException("source definition may not contain [{}]"; parser.text());
 }
 } else if (token == Token.START_ARRAY) {
 while ((token = parser.nextToken()) != Token.END_ARRAY) {
 currentList.add(parser.text());
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content