Wildcard queries cannot be executed when – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.7-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when a wildcard query is attempted on a field that is not analyzed. Elasticsearch wildcard queries are not allowed on non-analyzed fields because they are not tokenized, hence, they cannot be searched using wildcard patterns. To resolve this issue, you can either change the field to be analyzed or use a different type of query that does not require tokenization, such as a term or match query. Alternatively, you can use the keyword field which is automatically created for text fields if you still want to perform a wildcard search.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” [wildcard] queries 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 “[wildcard] queries cannot be executed when ‘” class name is StringFieldType.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 boolean shouldNormalize;
 SearchExecutionContext context
 ) {
 if (context.allowExpensiveQueries() == false) {
 throw new ElasticsearchException("[wildcard] queries cannot be executed when '" +
 ALLOW_EXPENSIVE_QUERIES.getKey() + "' is set to false.");
 }  Term term;
 if (getTextSearchInfo().getSearchAnalyzer() != null && shouldNormalize) {


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?