Dis_max query does not support ” + currentFieldName + ” – 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 ” dis_max 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 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 “[dis_max] query does not support [” + currentFieldName + “]”classname  is DisMaxQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else if (token == XContentParser.Token.START_OBJECT) {
 if (QUERIES_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 queriesFound = true;
 queries.add(parseInnerQueryBuilder(parser));
 } else {
 throw new ParsingException(parser.getTokenLocation(); "[dis_max] query does not support [" + currentFieldName + "]");
 }
 } else if (token == XContentParser.Token.START_ARRAY) {
 if (QUERIES_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 queriesFound = true;
 while (token != XContentParser.Token.END_ARRAY) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content