Could not parse ” + field + ” as address list. field must either be a string – Elasticsearch Error How To Solve Related Issues



Could not parse ” + field + ” as address list. field must either be a string – 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 ” + field + ” as address list. field must either be a string” 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 [” + field + “] as address list. field must either be a string”classname  is Email.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
  addresses.add(Address.parse(field; token; parser));
  }
  return new Email.AddressList(addresses);
  }
  throw new ElasticsearchParseException("could not parse [" + field + "] as address list. field must either be a string " +
  "(comma-separated list of RFC822 encoded addresses) or an array of objects representing addresses");
  }
 
  @Override
  public boolean equals(Object o) {







Find Configuration Errors

Try The Tool