Field must be either ; or – How to solve this Elasticsearch error

Average Read Time

2 Mins

Field must be either ; or – 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 ” field must be either ; or ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

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 “field must be either [{}]; [{}] or [{}]”classname  is GeoUtils.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

geohash = subParser.text();
 } else {
 throw new ElasticsearchParseException("geohash must be a string");
 }
 } else {
 throw new ElasticsearchParseException("field must be either [{}]; [{}] or [{}]"; LATITUDE; LONGITUDE; GEOHASH);
 }
 } else {
 throw new ElasticsearchParseException("token [{}] not allowed"; subParser.currentToken());
 }
 }

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content