Failed to find minimum_should_match field ” + minimumShouldMatchField + ” – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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 and index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

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

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content