Max_children is only supported on top level of nested sort – How to solve this Elasticsearch error

Average Read Time

2 Mins

Max_children is only supported on top level of nested sort – How to solve this Elasticsearch error

Opster Team

March-22, 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 ” max_children is only supported on top level of nested sort ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, sort.

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 “max_children is only supported on top level of nested sort”classname  is FieldSortBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

* Throws an exception if max children is not located at top level nested sort.
 */
 static void validateMaxChildrenExistOnlyInTopLevelNestedSort(SearchExecutionContext context; NestedSortBuilder nestedSort) {
 for (NestedSortBuilder child = nestedSort.getNestedSort(); child != null; child = child.getNestedSort()) {
 if (child.getMaxChildren() != Integer.MAX_VALUE) {
 throw new QueryShardException(context; "max_children is only supported on top level of nested sort");
 }
 }
 } 
 /**

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content