Unable to parse condition for watch . expected an empty object but found – Elasticsearch Error How To Solve Related Issues



Unable to parse condition for watch . expected an empty object but found – 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 “unable to parse condition for watch . expected an empty object but found” 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: plugin.


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”unable to parse [{}] condition for watch [{}]. expected an empty object but found [{}]”classname  is InternalAlwaysCondition.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

private InternalAlwaysCondition() { }
 
  public static InternalAlwaysCondition parse(String watchId; XContentParser parser) throws IOException {
  if (parser.currentToken() != XContentParser.Token.START_OBJECT) {
  throw new ElasticsearchParseException("unable to parse [{}] condition for watch [{}]. expected an empty object but found [{}]";
  TYPE; watchId; parser.currentName());
  }
  XContentParser.Token token = parser.nextToken();
  if (token != XContentParser.Token.END_OBJECT) {
  throw new ElasticsearchParseException("unable to parse [{}] condition for watch [{}]. expected an empty object but found [{}]";

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 Uncaught SyntaxError: Unexpected token u in JSON at position 0 -views 94,142 ,score 38

SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data -views   70,605,score 13



Find Configuration Errors

Analyze Now