Rescore doesn t support fieldName – 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 rescore query that is not supported. Rescoring is used to refine the top results returned by the query. The field you’re trying to use might not be indexed or might be of a type that is not compatible with the rescore query. To resolve this issue, you can check the field you’re using in your rescore query. Make sure it’s indexed and of a compatible type. If it’s not, you might need to reindex your data with the correct field type or use a different field in your rescore query.

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

Log Context

Log “rescore doesn’t support [” + fieldName + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 fieldName = parser.currentName();
 } else if (token.isValue()) {
 if (WINDOW_SIZE_FIELD.match(fieldName; parser.getDeprecationHandler())) {
 windowSize = parser.intValue();
 } else {
 throw new ParsingException(parser.getTokenLocation(); "rescore doesn't support [" + fieldName + "]");
 } else if (token == XContentParser.Token.START_OBJECT) {
 rescorer = parser.namedObject(RescorerBuilder.class; fieldName; null);
 } else {
 throw new ParsingException(parser.getTokenLocation(); "unexpected token [" + token + "] after [" + fieldName + "]");


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?