Expected ” + COMMA + ” but found: – How to solve this Elasticsearch error

Average Read Time

2 Mins

Expected ” + COMMA + ” but found: – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” expected ” + COMMA + ” but found: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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)) {

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content