Expected ” + XContentParser.Token.START_OBJECT + ” under – Elasticsearch Error How To Solve Related Issues



Expected ” + XContentParser.Token.START_OBJECT + ” under – 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 “Expected ” + XContentParser.Token.START_OBJECT + ” under” 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: parser, search, aggregations.


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”Expected [” + XContentParser.Token.START_OBJECT + “] under [“classname  is AggregatorFactories.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

SuggestingErrorOnUnknown.suggest(fieldName; ex.getCandidates()));
  throw new ParsingException(new XContentLocation(ex.getLineNumber(); ex.getColumnNumber()); message; ex);
  }
  }
  } else {
  throw new ParsingException(parser.getTokenLocation(); "Expected [" + XContentParser.Token.START_OBJECT + "] under ["
  + fieldName + "]; but got a [" + token + "] in [" + aggregationName + "]");
  }
  }
 
  if (aggBuilder == null) {

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 Elasticsearch json response to SearchResponse object …  

Elasticsearch json response to SearchResponse object …  



Find Configuration Errors

Analyze Now