Range query does not support currentFieldName – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when an unsupported field is used in a range query in Elasticsearch. The field specified in the range query is not recognized by Elasticsearch. To resolve this issue, you should first verify the field name in your range query. Make sure it matches exactly with the field name in your Elasticsearch index. If the field name is correct, check the field type. Not all field types are supported in range queries. For instance, text fields are not allowed in range queries. You may need to change the field type or use a different query type.

This guide will help you check for common problems that cause the log ” [range] query does not support [” + currentFieldName + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query, index.

Log Context

Log “[range] query does not support [” + currentFieldName + “]” class name is RangeQueryBuilder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (token.isValue()) {
 throw new ParsingException(parser.getTokenLocation(); "[range] query does not support [" + currentFieldName + "]");
 }  RangeQueryBuilder rangeQuery = new RangeQueryBuilder(fieldName);


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?