Only two values lon; lat expected – How to solve this Elasticsearch error

Average Read Time

2 Mins

Only two values lon; lat expected – 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 ” only two values lon; lat expected ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search.

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 “only two values [lon; lat] expected”classname  is GeoContextMapping.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (parser.nextToken() == Token.VALUE_NUMBER) {
 double lat = parser.doubleValue();
 if (parser.nextToken() == Token.END_ARRAY) {
 contexts.add(stringEncode(lon; lat; precision));
 } else {
 throw new ElasticsearchParseException("only two values [lon; lat] expected");
 }
 } else {
 throw new ElasticsearchParseException("latitude must be a numeric value");
 }
 } else {

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content