No text specified for multi_match query – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” No text specified for multi_match query ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query and index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “No text specified for multi_match query”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

"[" + NAME + "] unknown token [" + token + "] after [" + currentFieldName + "]");
 if (value == null) {
 throw new ParsingException(parser.getTokenLocation(); "No text specified for multi_match query");
 if (fuzziness != null && (type == Type.CROSS_FIELDS || type == Type.PHRASE || type == Type.PHRASE_PREFIX)) {
 throw new ParsingException(parser.getTokenLocation();
 "Fuzziness not allowed for type [" + type.parseField.getPreferredName() + "]");


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content