Could not parse condition for watch . invalid definition. expected a field – Elasticsearch Error How To Solve Related Issues



Could not parse condition for watch . invalid definition. expected a field – 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 condition for watch . invalid definition. expected a field” 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”could not parse condition for watch [{}]. invalid definition. expected a field”classname  is ConditionRegistry.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

XContentParser.Token token;
  while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
  if (token == XContentParser.Token.FIELD_NAME) {
  type = parser.currentName();
  } else if (type == null) {
  throw new ElasticsearchParseException("could not parse condition for watch [{}]. invalid definition. expected a field " +
  "indicating the condition type; but found"; watchId; token);
  } else {
  factory = factories.get(type);
  if (factory == null) {
  throw new ElasticsearchParseException("could not parse condition for watch [{}]. unknown condition type [{}]";

 

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 JSON -views 355,481 ,score 295

json: cannot unmarshal object into Go value of type -views   89,602,score 22

 

 

About Opster

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

Find Configuration Errors

Analyze Now