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

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

if (isNumberNext(stream) || (isOpenParen = nextWord(stream).equals(LPAREN))) {
  coordinates.coordinate(parseCoordinate(stream; ignoreZValue; coerce));
  if (isOpenParen && nextCloser(stream).equals(RPAREN) == false) {
  throw new ElasticsearchParseException("expected: [{}]" + RPAREN + " but found: [{}]" + tokenString(stream); stream.lineno());
  while (nextCloserOrComma(stream).equals(COMMA)) {
  isOpenParen = false;
  if (isNumberNext(stream) || (isOpenParen = nextWord(stream).equals(LPAREN))) {

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 Java format yyyy-MM-dd'T'HH:mm:ss.SSSz to yyyy-mm-dd HH:mm:ss -views 296,808 ,score 50

Spring MVC "Request processing failed" 500 error -views   34,182,score 1

Find Configuration Errors

Analyze Now