Could not parse condition for watch . compared value for with – Elasticsearch Error How To Solve Related Issues

Could not parse condition for watch . compared value for with – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, 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 that cause many errors.

This guide will help you check for common problems that cause the log ” could not parse condition for watch . compared value for with ” 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”could not parse [{}] condition for watch [{}]. compared value for [{}] with”classname  is CompareCondition.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new ElasticsearchParseException("could not parse [{}] condition for watch [{}]. unknown comparison operator " +
  "[{}]"; TYPE; watchId; parser.currentName());
  }
  token = parser.nextToken();
  if (!op.supportsStructures() && !token.isValue() && token != XContentParser.Token.VALUE_NULL) {
  throw new ElasticsearchParseException("could not parse [{}] condition for watch [{}]. compared value for [{}] with " +
  "operation [{}] must either be a numeric; string; boolean or null value; but found [{}] instead"; TYPE;
  watchId; path; op.name().toLowerCase(Locale.ROOT); token);
  }
  value = XContentUtils.readValue(parser; token);
  token = parser.nextToken();

 

Optimize Elasticsearch Performance

Try The Tool