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 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 ” 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.

Log Context

Log “source definition may not contain [{}]”classname  is 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) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content