Expected ” + COMMA + ” but found: – Elasticsearch Error How To Solve Related Issues



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

private static String nextComma(StreamTokenizer stream) throws IOException; ElasticsearchParseException {
  if (nextWord(stream).equals(COMMA)) {
  return COMMA;
  }
  throw new ElasticsearchParseException("expected " + COMMA + " but found: " + tokenString(stream); stream.lineno());
  }
 
  private static String nextCloserOrComma(StreamTokenizer stream) throws IOException; ElasticsearchParseException {
  String token = nextWord(stream);
  if (token.equals(COMMA) || token.equals(RPAREN)) {

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 Possible cases for Javascript error: "Expected identifier, string or number" -views 188,562 ,score 84

expected declaration, found 'IDENT' item -views   20,712,score 20



Find Configuration Errors

Analyze Now