Could not parse trigger for . expected END_OBJECT token; but found – Elasticsearch Error How To Solve Related Issues



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

" but found [{}]"; type; jobName; token);
  }
  Trigger trigger = parseTrigger(jobName; type; parser);
  token = parser.nextToken();
  if (token != XContentParser.Token.END_OBJECT) {
  throw new ElasticsearchParseException("could not parse trigger [{}] for [{}]. expected [END_OBJECT] token; but found [{}]";
  type; jobName; token);
  }
  return trigger;
  }







Find Configuration Errors

Try The Tool