Longitude must be a number – How to solve this Elasticsearch error

Average Read Time

2 Mins

Longitude must be a number – 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 ” longitude must be a number ” 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 “longitude must be a number”classname  is GeoPoint.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new ElasticsearchParseException("latitude must be a number");
 }
 try {
 lon = Double.parseDouble(vals[1].trim());
 } catch (NumberFormatException ex) {
 throw new ElasticsearchParseException("longitude must be a number");
 }
 if (vals.length > 2) {
 GeoPoint.assertZValue(ignoreZValue; Double.parseDouble(vals[2].trim()));
 }
 return reset(lat; lon);

 

Watch a demo of the Check-Up:

Analyze your cluster