Expected ” + COMMA + ” or – How to solve this Elasticsearch error

Expected ” + COMMA + ” or – 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 Error 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 + ” 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: Node.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (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 {


Run the Check-Up to get a customized report like this:

Analyze your cluster