Nested_path has been removed in favour of the nested parameter – 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 ” nested_path has been removed in favour of the nested parameter ” 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 “[nested_path] has been removed in favour of the [nested] parameter”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

PARSER.declareString(FieldSortBuilder::setNumericType; NUMERIC_TYPE);
 PARSER.declareString(FieldSortBuilder::setFormat; FORMAT);
 (b; v) -> {};
 (p; c) -> {
 throw new ParsingException(p.getTokenLocation(); "[nested_path] has been removed in favour of the [nested] parameter"; c);


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content