[ https://issues.apache.org/jira/browse/SPARK-28375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023695#comment-17023695 ]
Takeshi Yamamuro commented on SPARK-28375: ------------------------------------------ IMO PullupCorrelatedPredicates is in the catalyst package and the object seems to be internal. If so, I think its less worth backpoiting this to branch-2.4. > Enforce idempotence on the PullupCorrelatedPredicates optimizer rule > -------------------------------------------------------------------- > > Key: SPARK-28375 > URL: https://issues.apache.org/jira/browse/SPARK-28375 > Project: Spark > Issue Type: Improvement > Components: SQL > Affects Versions: 3.0.0 > Reporter: Yesheng Ma > Assignee: Dilip Biswal > Priority: Major > Labels: correctness > Fix For: 3.0.0 > > > The current PullupCorrelatedPredicates implementation can accidentally remove > predicates for multiple runs. > For example, for the following logical plan, one more optimizer run can > remove the predicate in the SubqueryExpresssion. > {code:java} > # Optimized > Project [a#0] > +- Filter a#0 IN (list#4 [(b#1 < d#3)]) > : +- Project [c#2, d#3] > : +- LocalRelation <empty>, [c#2, d#3] > +- LocalRelation <empty>, [a#0, b#1] > # Double optimized > Project [a#0] > +- Filter a#0 IN (list#4 []) > : +- Project [c#2, d#3] > : +- LocalRelation <empty>, [c#2, d#3] > +- LocalRelation <empty>, [a#0, b#1] > {code} > > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org