dilipbiswal commented on a change in pull request #25164: [SPARK-28375] Prevent
the PullupCorrelatedPredicates optimizer rule from removing predicates if run
multiple times
URL: https://github.com/apache/spark/pull/25164#discussion_r303762504
##########
File path:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/subquery.scala
##########
@@ -275,13 +275,16 @@ object PullupCorrelatedPredicates extends
Rule[LogicalPlan] with PredicateHelper
plan transformExpressions {
case ScalarSubquery(sub, children, exprId) if children.nonEmpty =>
val (newPlan, newCond) = pullOutCorrelatedPredicates(sub, outerPlans)
- ScalarSubquery(newPlan, newCond, exprId)
+ val conds = newCond ++ children.filter(_.isInstanceOf[Predicate])
Review comment:
@yeshengm A couple of questions.
1. Given this rule is run once, do we have a problem in real-life ? Or we
just want to make sure things would be okay if this got fired more than one
time ?
2. I am also little hesitant on using Predicate check like @mgaido91. Should
we check if the subplan has outer references and if not, just return the
original expression ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
