Failed to find minimum should match field minimumShouldMatchField – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch cannot locate the “minimum_should_match” field in a query. This field is used to specify the minimum number of optional boolean clauses that must match for a document to be considered relevant. To resolve this issue, ensure that the “minimum_should_match” field is correctly defined in your query. Also, check for any typographical errors in the field name. If the field is not required, consider removing it from your query. Lastly, ensure that the field is supported in your version of Elasticsearch.

This guide will help you check for common problems that cause the log ” failed to find minimum_should_match field [” + minimumShouldMatchField + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query, index.

Log Context

Log “failed to find minimum_should_match field [” + minimumShouldMatchField + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 private LongValuesSource createValuesSource(SearchExecutionContext context) {
 LongValuesSource longValuesSource;
 if (minimumShouldMatchField != null) {
 MappedFieldType msmFieldType = context.getFieldType(minimumShouldMatchField);
 if (msmFieldType == null) {
 throw new QueryShardException(context; "failed to find minimum_should_match field [" + minimumShouldMatchField + "]");
 }  IndexNumericFieldData fieldData = context.getForField(msmFieldType; MappedFieldType.FielddataOperation.SEARCH);
 longValuesSource = new FieldValuesSource(fieldData);
 } else if (minimumShouldMatchScript != null) {


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?