Expected end of WKT string but found additional text: – How to solve this Elasticsearch error

Average Read Time

2 Mins

Expected end of WKT string but found additional text: – 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 end of WKT string but found additional text: ” 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 end of WKT string but found additional text:”classname  is GeoWKTParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} 
 /** next word in the stream */
 private static void checkEOF(StreamTokenizer stream) throws ElasticsearchParseException; IOException {
 if (stream.nextToken() != StreamTokenizer.TT_EOF) {
 throw new ElasticsearchParseException("expected end of WKT string but found additional text: "
 + tokenString(stream); stream.lineno());
 }
 }
 }

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content