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

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

return word.equalsIgnoreCase(EMPTY) ? EMPTY : word;
  case '(': return LPAREN;
  case ')': return RPAREN;
  case ';': return COMMA;
  throw new ElasticsearchParseException("expected word but found: " + tokenString(stream); stream.lineno());
  private static double nextNumber(StreamTokenizer stream) throws IOException; ElasticsearchParseException {
  if (stream.nextToken() == StreamTokenizer.TT_WORD) {
  if (stream.sval.equalsIgnoreCase(NAN)) {

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 malformed query, expected END_OBJECT but found FIELD_NAME error in Kibana (Elastic Search) -views 29,553 ,score 14

elasticsearch synonyms not working as expected -views   829,score 1

Find Configuration Errors

Analyze Now