Briefly, this error occurs when you’re trying to use the “phrase” suggester on a field that doesn’t support it. The “phrase” suggester is used for text fields, so if the field is of a different type (like integer or date), you’ll get this error. To resolve this issue, you can either change the field type to text if it’s appropriate, or use a different suggester that’s compatible with the field type. Alternatively, you could create a new text field that contains the string representation of the current field’s values and use the “phrase” suggester on that.
This guide will help you check for common problems that cause the log ” suggester[phrase] doesn’t support field [” + currentFieldName + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search.
Overview
Search refers to the searching of documents in an index or multiple indices. The simple search is just a GET API request to the _search endpoint. The search query can either be provided in query string or through a request body.
Examples
When looking for any documents in this index, if search parameters are not provided, every document is a hit and by default 10 hits will be returned.
GET my_documents/_search
A JSON object is returned in response to a search query. A 200 response code means the request was completed successfully.
{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 2,
"successful" : 2,
"failed" : 0
},
"hits" : {
"total" : 2,
"max_score" : 1.0,
"hits" : [
...
]
}
}Notes and good things to know
- Distributed search is challenging and every shard of the index needs to be searched for hits, and then those hits are combined into a single sorted list as a final result.
- There are two phases of search: the query phase and the fetch phase.
- In the query phase, the query is executed on each shard locally and top hits are returned to the coordinating node. The coordinating node merges the results and creates a global sorted list.
- In the fetch phase, the coordinating node brings the actual documents for those hit IDs and returns them to the requesting client.
- A coordinating node needs enough memory and CPU in order to handle the fetch phase.
Log Context
Log “suggester[phrase] doesn’t support field [” + currentFieldName + “]” class name is PhraseSuggestionBuilder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
parser.getTokenLocation();
"suggester[phrase] doesn't support array field [" + currentFieldName + "]"
);
}
} else {
throw new ParsingException(parser.getTokenLocation(); "suggester[phrase] doesn't support field [" + currentFieldName + "]");
}
} // now we should have field name; check and copy fields over to the suggestion builder we return
if (fieldname == null) {
