Geohash must be a string – Elasticsearch Error How To Solve Related Issues

Geohash must be a string – 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 “geohash must be a string” 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”geohash must be a string”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

  } else if (GEOHASH.equals(field)) {
  if (subParser.nextToken() == Token.VALUE_STRING) {
  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 {

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 How to use geo_point with geohash in Elasticsearch with a Java class? -views 10,982 ,score 5

Does Mongo-connector supports adding fields before inserting to Elasticsearch? -views   1,376,score 1

Find Configuration Errors

Analyze Now