[ 
https://issues.apache.org/jira/browse/SPARK-32986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dongjoon Hyun resolved SPARK-32986.
-----------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

Issue resolved by pull request 33698
[https://github.com/apache/spark/pull/33698]

> Add bucket scan info in explain output of FileSourceScanExec
> ------------------------------------------------------------
>
>                 Key: SPARK-32986
>                 URL: https://issues.apache.org/jira/browse/SPARK-32986
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.1.0
>            Reporter: Cheng Su
>            Assignee: Cheng Su
>            Priority: Trivial
>             Fix For: 3.3.0
>
>
> As a followup from discussion in 
> [https://github.com/apache/spark/pull/29804#discussion_r493229395] , 
> currently for `FileSourceScanExec` explain output, there's no information to 
> indicate whether the table is read as bucketed table. And if not read as 
> bucketed table, what's the reason behind it. Add this info into 
> `FileSourceScanExec` explain output, can help users/developers understand 
> query plan more easily without spending a lot of time debugging why table is 
> not read as bucketed table.



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

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

Reply via email to