No found for value – Elasticsearch Error How To Solve Related Issues

No found for value – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing 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, 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 discover the cause of many errors and provides suitable actionable recommendations (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);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 No mapping found for field in order to sort on in ElasticSearch -views 66,916 ,score 115

HttpClient not found in elastic4s? -views   342,score 2

Find Configuration Errors

Analyze Now