You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Eugene Koifman (Jira)" <ji...@apache.org> on 2020/12/17 22:09:00 UTC

[jira] [Created] (SPARK-33832) Add an option in AQE to mitigate skew even if it causes an new shuffle

Eugene Koifman created SPARK-33832:
--------------------------------------

             Summary: Add an option in AQE to mitigate skew even if it causes an new shuffle
                 Key: SPARK-33832
                 URL: https://issues.apache.org/jira/browse/SPARK-33832
             Project: Spark
          Issue Type: Improvement
          Components: SQL
    Affects Versions: 3.0.0
            Reporter: Eugene Koifman


Currently {{OptimizeSkewJoin}} will not apply if skew mitigation causes a new shuffle.
There are situations where it's better to mitigate skew even if it means a new shuffle is added, for example if the join outputs small amount of data.

As a first step I propose adding a SQLConf option to enable this.  

I'll open a PR shortly to get feedback on the approach.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org