Suggestion does not support currentFieldName – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when you’re trying to use a field in the Elasticsearch suggestion API that is not supported. The field name causing the issue is represented by “currentFieldName”. To resolve this, ensure that the field you’re trying to use is supported by the suggestion API. You may need to modify your query to use a different field or adjust your index mapping to make the field compatible with the suggestion API. Also, check for typos or incorrect field names in your query.

This guide will help you check for common problems that cause the log ” suggestion does not support [” + currentFieldName + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search.

Log Context

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

 } else if (PREFIX_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 prefix = parser.text();
 } else if (REGEX_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 regex = parser.text();
 } else {
 throw new ParsingException(parser.getTokenLocation(); "suggestion does not support [" + currentFieldName + "]");
 } else if (token == XContentParser.Token.START_OBJECT) {
 suggestionBuilder = parser.namedObject(SuggestionBuilder.class; currentFieldName; null);


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?