Span first query does not support currentFieldName – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when an unsupported field is used in the span_first query in Elasticsearch. The span_first query only supports “match” and “end” fields. If you use any other field, it will throw this error. To resolve this issue, ensure that you are only using the supported fields in your span_first query. If you need to use other fields, consider using a different type of query that supports those fields.

This guide will help you check for common problems that cause the log ” [span_first] 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, index.

Log Context

Log “[span_first] query does not support [” + currentFieldName + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new ParsingException(parser.getTokenLocation(); "span_first [match] must be of type span query");
 match = (SpanQueryBuilder) query;
 checkNoBoost(NAME; currentFieldName; parser; match);
 } else {
 throw new ParsingException(parser.getTokenLocation(); "[span_first] query does not support [" + currentFieldName + "]");
 } else {
 if (AbstractQueryBuilder.BOOST_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 boost = parser.floatValue();
 } else if (END_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {


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?