Could not parse trigger for . expected trigger type string field; but found – 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 trigger for . expected trigger type string field; but found ” 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 trigger for [{}]. expected trigger type string field; but found [{}]”classname  is TriggerService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public Trigger parseTrigger(String jobName; XContentParser parser) throws IOException {
 XContentParser.Token token = parser.currentToken();
 assert token == XContentParser.Token.START_OBJECT;
 token = parser.nextToken();
 if (token != XContentParser.Token.FIELD_NAME) {
 throw new ElasticsearchParseException("could not parse trigger for [{}]. expected trigger type string field; but found [{}]";
 jobName; token);
 }
 String type = parser.currentName();
 token = parser.nextToken();
 if (token != XContentParser.Token.START_OBJECT) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content