Could not parse ” + field + ” as address list. field must either be a string – 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 ” + field + ” as address list. field must either be a string ” 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 [” + 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) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content