You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2021/09/13 09:23:00 UTC
[jira] [Resolved] (SPARK-33832) Add an option in AQE to mitigate
skew even if it causes an new shuffle
[ https://issues.apache.org/jira/browse/SPARK-33832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-33832.
---------------------------------
Fix Version/s: 3.3.0
Resolution: Fixed
Issue resolved by pull request 32816
[https://github.com/apache/spark/pull/32816]
> 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: Sub-task
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Eugene Koifman
> Priority: Major
> Fix For: 3.3.0
>
>
> Currently {{OptimizeSkewedJoin}} 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