You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Zhen Wang (Jira)" <ji...@apache.org> on 2024/07/05 07:00:00 UTC
[jira] [Updated] (SPARK-48817) MultiInsert is split to multiple sql executions, resulting in no exchange reuse
[ https://issues.apache.org/jira/browse/SPARK-48817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhen Wang updated SPARK-48817:
------------------------------
Attachment: image-2024-07-05-14-59-55-291.png
> MultiInsert is split to multiple sql executions, resulting in no exchange reuse
> -------------------------------------------------------------------------------
>
> Key: SPARK-48817
> URL: https://issues.apache.org/jira/browse/SPARK-48817
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 4.0.0, 3.5.1
> Reporter: Zhen Wang
> Priority: Major
> Attachments: image-2024-07-05-14-59-35-340.png, image-2024-07-05-14-59-55-291.png
>
>
> MultiInsert is split to multiple sql executions, resulting in no exchange reuse.
>
> Reproduce sql:
>
> {code:java}
> create table wangzhen_t1(c1 int);
> create table wangzhen_t2(c1 int);
> create table wangzhen_t3(c1 int);from (select /*+ REPARTITION(3) */ c1 from wangzhen_t1)
> insert overwrite table wangzhen_t2 select c1
> insert overwrite table wangzhen_t3 select c1; {code}
>
>
> In Spark 3.1, there is only one SQL execution and there is a reuse exchange.
> !image-2024-07-05-14-59-35-340.png!
> However, in Spark 3.5, it was split to multiple executions and there was no ReuseExchange.
> !image-2024-07-05-14-58-45-544.png!
> !image-2024-07-05-14-58-01-236.png!!image-2024-07-05-14-58-10-089.png!!image-2024-07-05-14-58-29-826.png!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org