More_like_this requires ‘fields’ to be non-empty – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” more_like_this requires ‘fields’ to be non-empty ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query and index.

Log Context

Log “more_like_this requires ‘fields’ to be non-empty”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (likeTexts.isEmpty() && likeItems.isEmpty()) {
 throw new ParsingException(parser.getTokenLocation(); "more_like_this requires 'like' to be specified");
 if (fields != null && fields.isEmpty()) {
 throw new ParsingException(parser.getTokenLocation(); "more_like_this requires 'fields' to be non-empty");
 String[] fieldsArray = fields == null ? null : fields.toArray(new String[fields.size()]);
 String[] likeTextsArray = likeTexts.isEmpty() ? null : likeTexts.toArray(new String[likeTexts.size()]);
 String[] unlikeTextsArray = unlikeTexts.isEmpty() ? null : unlikeTexts.toArray(new String[unlikeTexts.size()]);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content