Expected number but found: – Elasticsearch Error How To Solve Related Issues



Expected number but found: – 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 “expected number but found:” 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”expected number but found:”classname  is GeoWKTParser.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} catch (NumberFormatException e) {
  throw new ElasticsearchParseException("invalid number found: " + stream.sval; stream.lineno());
  }
  }
  }
  throw new ElasticsearchParseException("expected number but found: " + tokenString(stream); stream.lineno());
  }
 
  private static String tokenString(StreamTokenizer stream) {
  switch (stream.ttype) {
  case StreamTokenizer.TT_WORD: return stream.sval;

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 GSON throwing "Expected BEGIN_OBJECT but was BEGIN_ARRAY"? -views 421,128 ,score 296

BULK API : Malformed action/metadata line [3], expected START_OBJECT but found [VALUE_STRING] -views   11,126,score 10



Find Configuration Errors

Analyze Now