Expected ” + COMMA + ” or – Elasticsearch Error How To Solve Related Issues

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

private static String nextCloserOrComma(StreamTokenizer stream) throws IOException; ElasticsearchParseException {
  String token = nextWord(stream);
  if (token.equals(COMMA) || token.equals(RPAREN)) {
  return token;
  throw new ElasticsearchParseException("expected " + COMMA + " or " + RPAREN
  + " but found: " + tokenString(stream); stream.lineno());
  /** next word in the stream */
  private static void checkEOF(StreamTokenizer stream) throws ElasticsearchParseException; IOException {

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 {"errorMessages":["Unexpected character (''' (code 39)): expected a valid value -views 18,626 ,score 13

Elasticsearch: Expected field name but got START_OBJECT -views   6,812,score 3

Find Configuration Errors

Analyze Now