Failed to parse ; expected 2 or 3 coordinates – Elasticsearch Error How To Solve Related Issues



Failed to parse ; expected 2 or 3 coordinates – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 

 

This guide will help you check for common problems that cause the log “failed to parse ; expected 2 or 3 coordinates” 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: .


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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”failed to parse [{}]; expected 2 or 3 coordinates”classname  is GeoPoint.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public GeoPoint resetFromCoordinates(String value; final boolean ignoreZValue) {
  String[] vals = value.split(";");
  if (vals.length > 3) {
  throw new ElasticsearchParseException("failed to parse [{}]; expected 2 or 3 coordinates "
  + "but found: [{}]"; vals.length);
  }
  final double lat;
  final double lon;
  try {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Index twitter data with coordinates geo_point parse exception …  

Index twitter data with coordinates geo_point parse exception …  



Find Configuration Errors

Analyze Now