Could not parse inner _source definition – Elasticsearch Error How To Solve Related Issues

Could not parse inner _source definition – 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 “Could not parse inner _source definition” 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: query, index.

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”Could not parse inner _source definition”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

  PARSER.declareField((p; i; c) -> {
  try {
  } catch (IOException e) {
  throw new ParsingException(p.getTokenLocation(); "Could not parse inner _source definition"; e);
  }; SearchSourceBuilder._SOURCE_FIELD; ObjectParser.ValueType.OBJECT_ARRAY_BOOLEAN_OR_STRING);
  PARSER.declareObject(InnerHitBuilder::setHighlightBuilder; (p; c) -> HighlightBuilder.fromXContent(p);
  PARSER.declareField((parser; builder; context) -> {


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 JSON parse error: Can not construct instance of java.time.LocalDate: no String-argument constructor/factory method to deserialize from String value -views 72,889 ,score 42

Logstash does not parse json -views   27,188,score 10



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now