From ccf7302d21c292c33e4947b2a225f9b0b3e3c786 Mon Sep 17 00:00:00 2001 From: Bruce Robbins Date: Tue, 26 Nov 2024 17:44:30 -0800 Subject: [PATCH] Address review comments --- .../org/apache/spark/sql/catalyst/optimizer/subquery.scala | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/subquery.scala b/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/subquery.scala index 9429419fdcfce..9c5317084b2b6 100644 --- a/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/subquery.scala +++ b/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/subquery.scala @@ -292,7 +292,7 @@ object RewritePredicateSubquery extends Rule[LogicalPlan] with PredicateHelper { // +- LocalRelation [col1#28, col2#29] // // Note that the Aggregate node contains the IN-subquery and the left-hand - // side of the IN-subquery is an aggregate expression (sum(col2#28)). + // side of the IN-subquery is an aggregate expression (sum(col2#29)). // // This handler transforms the above plan into the following: // @@ -303,7 +303,7 @@ object RewritePredicateSubquery extends Rule[LogicalPlan] with PredicateHelper { // // The transformation pulled the IN-subquery up into a Project. The left-hand side of the // IN-subquery is now an attribute (sum(col2)#36L) that refers to the actual aggregation - // which is still performed in the Aggregate node (sum(col2#28) AS sum(col2)#36L). The Unary + // which is still performed in the Aggregate node (sum(col2#29) AS sum(col2)#36L). The Unary // node handler will use that attribute in the join condition (rather than the aggregate // expression). //