Only two values lon; lat expected – Elasticsearch Error How To Solve Related Issues


Only two values lon; lat expected – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: search.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 {

 

Optimize Elasticsearch Performance

Try The Tool