You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "mcdull_zhang (Jira)" <ji...@apache.org> on 2021/12/15 12:21:00 UTC
[jira] [Updated] (SPARK-37652) Support optimize skewed join through union
[ 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org