Range queries on text or keyword fields cannot be executed when – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.7-7.15

Briefly, this error occurs when a range query is attempted on text or keyword fields while the ‘fielddata’ is disabled. Fielddata is usually disabled because it can consume a lot of heap space. To resolve this issue, you can either enable ‘fielddata’ on the specific field, but be aware of the potential memory impact. Alternatively, you can change the field type to a type that supports sorting or scripting out of the box, such as ‘integer’ or ‘date’. Another solution is to use a ‘doc_values’ field instead, which is a disk-based data structure and doesn’t consume heap space.

This guide will help you check for common problems that cause the log ” [range] queries on [text] or [keyword] fields cannot be executed when ‘ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “[range] queries on [text] or [keyword] fields cannot be executed when ‘” class name is StringFieldType.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public Query rangeQuery(Object lowerTerm; Object upperTerm; boolean includeLower; boolean includeUpper;
 SearchExecutionContext context) {
 if (context.allowExpensiveQueries() == false) {
 throw new ElasticsearchException("[range] queries on [text] or [keyword] fields cannot be executed when '" +
 ALLOW_EXPENSIVE_QUERIES.getKey() + "' is set to false.");
 return new TermRangeQuery(name();
 lowerTerm == null ? null : indexedValueForSearch(lowerTerm);