Could not parse input for watch . expected field indicating the input type; – Elasticsearch Error How To Solve Related Issues



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

ExecutableInput; ?> input = null;
  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 input for watch [{}]. expected field indicating the input type; " +
  "but found [{}] instead"; watchId; token);
  } else if (token == XContentParser.Token.START_OBJECT) {
  InputFactory; ?; ?> factory = factories.get(type);
  if (factory == null) {
  throw new ElasticsearchParseException("could not parse input for watch [{}]. unknown input type [{}]"; watchId; 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,485 ,score 295

Watcher input extract fields – Elasticsearch – Discuss the Elastic Stack  

 

 

About Opster

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

Find Configuration Errors

Analyze Now