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 Elasticsearch encounters an unsupported field in the query. This could be due to a typo in the field name, or the field might not exist in the index. To resolve this issue, you can check the field name for typos, ensure the field exists in the index, or update your index mapping to include the field. If the field is not necessary, you can remove it from the query.

This guide will help you check for common problems that cause the log ” 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 “query does not support [” + currentFieldName + “]” class name is AbstractGeometryQueryBuilder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 "unknown token [" + token + "] after [" + currentFieldName + "]"
 } else {
 throw new ParsingException(parser.getTokenLocation(); "query does not support [" + currentFieldName + "]");
 } else if (token.isValue()) {
 if (AbstractQueryBuilder.BOOST_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {