Could not parse field object as address unknown address – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is unable to parse a field as an address because the address is unknown or not recognized. This could be due to incorrect formatting or a typo in the address. To resolve this issue, you can check the format of the address and ensure it matches the expected format. Also, verify that the address exists and is correctly spelled. If the error persists, consider reindexing the data to ensure there are no inconsistencies or errors in the data.

This guide will help you check for common problems that cause the log ” could not parse [” + field + “] object as address. unknown address ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “could not parse [” + field + “] object as address. unknown address ” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (ADDRESS_EMAIL_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 email = parser.text();
 } else if (ADDRESS_NAME_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 name = parser.text();
 } else {
 throw new ElasticsearchParseException("could not parse [" + field + "] object as address. unknown address " +
 "field [" + currentFieldName + "]");
 if (email == null) {