Span_not query does not support ” + currentFieldName + ” – How to solve this Elasticsearch error

Span_not 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 Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” span_not query does not support ” + currentFieldName + ” ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”[span_not] query does not support [” + currentFieldName + “]”classname  is SpanNotQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new ParsingException(parser.getTokenLocation(); "span_not [exclude] must be of type span query");
  }
  exclude = (SpanQueryBuilder) query;
  checkNoBoost(NAME; currentFieldName; parser; exclude);
  } else {
  throw new ParsingException(parser.getTokenLocation(); "[span_not] query does not support [" + currentFieldName + "]");
  }
  } else {
  if (DIST_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
  dist = parser.intValue();
  } else if (PRE_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {

 

Run the Check-Up to get a customized report like this:

Analyze your cluster