Failed to parse action /. expected to be of type string; but – Elasticsearch Error How To Solve Related Issues



Failed to parse action /. expected to be of type string; but – 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 “failed to parse action /. expected to be of type string; but” 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”failed to parse [{}] action [{}/{}]. expected [{}] to be of type string; but”classname  is JiraAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

currentFieldName = parser.currentName();
  } else if (Field.ACCOUNT.match(currentFieldName; parser.getDeprecationHandler())) {
  if (token == XContentParser.Token.VALUE_STRING) {
  account = parser.text();
  } else {
  throw new ElasticsearchParseException("failed to parse [{}] action [{}/{}]. expected [{}] to be of type string; but " +
  "found [{}] instead"; TYPE; watchId; actionId; Field.ACCOUNT.getPreferredName(); token);
  }
  } else if (Field.PROXY.match(currentFieldName; parser.getDeprecationHandler())) {
  proxy = HttpProxy.parse(parser);
  } else if (Field.FIELDS.match(currentFieldName; parser.getDeprecationHandler())) {

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 Elastic Search : Expected numeric type on field -views 6,209 ,score 3

elasticsearch: create index with mappings -views   5,518,score 3



Find Configuration Errors

Analyze Now