[ https://issues.apache.org/jira/browse/SPARK-37652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
mcdull_zhang updated SPARK-37652: --------------------------------- Description: `OptimizeSkewedJoin` rule will take effect only when the plan has two ShuffleQueryStageExec。 With `Union`, it might break the assumption. For example, the following plans {code:tex} // Some comments here public String getFoo() { return foo; } {code} was: `OptimizeSkewedJoin` rule will take effect only when the plan has two ShuffleQueryStageExec。 With `Union`, it might break the assumption. For example, the following plans {panel:title=scenes1:} Union SMJ SMJ {panel} > Support optimize skewed join through union > ------------------------------------------ > > Key: SPARK-37652 > URL: https://issues.apache.org/jira/browse/SPARK-37652 > Project: Spark > Issue Type: Sub-task > Components: SQL > Affects Versions: 3.2.0 > Reporter: mcdull_zhang > Priority: Minor > > `OptimizeSkewedJoin` rule will take effect only when the plan has two > ShuffleQueryStageExec。 > With `Union`, it might break the assumption. For example, the following plans > {code:tex} > // Some comments here > public String getFoo() > { > return foo; > } > {code} -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org