No found for value – How to solve this Elasticsearch error

Average Read Time

2 Mins

No found for value – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” no found for value ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: search and aggregations.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”no [{}] found for value [{}]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

for (SubAggCollectionMode mode : modes) {
  if (mode.parseField.match(value; deprecationHandler)) {
  return mode;
  throw new ElasticsearchParseException("no [{}] found for value [{}]"; KEY.getPreferredName(); value);
  public static SubAggCollectionMode readFromStream(StreamInput in) throws IOException {
  return in.readEnum(SubAggCollectionMode.class);


Run the Check-Up to get a customized report like this:

Analyze your cluster