Expected number but found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch expects a numeric value in a specific field but encounters a different data type, such as a string or boolean. This mismatch can occur during indexing or querying data. To resolve this, ensure that the data type of the field matches the expected numeric type. You can also use the “ignore_malformed” option to ignore such errors during indexing. Additionally, consider using a script to convert non-numeric values into numeric ones before indexing.

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

Log Context

Log “expected number but found:” class name is GeoWKTParser.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } catch (NumberFormatException e) {
 throw new ElasticsearchParseException("invalid number found: " + stream.sval; stream.lineno());
 throw new ElasticsearchParseException("expected number but found: " + tokenString(stream); stream.lineno());
 }  private static String tokenString(StreamTokenizer stream) {
 return switch (stream.ttype) {
 case StreamTokenizer.TT_WORD -> stream.sval;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?