Source definition may not contain – Elasticsearch Error How To Solve Related Issues

Source definition may not contain – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “source definition may not contain” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: source.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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) {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Error: Selection does not contain a main type -views 221,806 ,score 56

'IServiceCollection' does not contain a definition for 'AddSession' -views   25,132,score 10

Find Configuration Errors

Analyze Now