Could not parse condition for watch . expected a – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch 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 . expected a ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “could not parse [{}] condition for watch [{}]. expected a”classname  is ArrayCompareCondition.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 [{}]. " +
 "expected a field indicating the comparison value or comparison quantifier; but found" +
 " [{}] instead"; TYPE; watchId; parser.currentName());
 }
 } else {
 throw new ElasticsearchParseException("could not parse [{}] condition for watch [{}]. expected a " +
 "field indicating the comparison value or comparison quantifier; but found [{}] instead";
 TYPE; watchId; token);
 }
 }
 } else {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content