[jira] [Resolved] (SPARK-26661) Show actual class name of the writing command in CTAS explain

["Dongjoon Hyun (JIRA)" <ji...@apache.org>]

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

Dongjoon Hyun resolved SPARK-26661.
-----------------------------------
       Resolution: Fixed
         Assignee: Kris Mok
    Fix Version/s: 3.0.0

This is resolved via https://github.com/apache/spark/pull/23582

> Show actual class name of the writing command in CTAS explain
> -------------------------------------------------------------
>
>                 Key: SPARK-26661
>                 URL: https://issues.apache.org/jira/browse/SPARK-26661
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Kris Mok
>            Assignee: Kris Mok
>            Priority: Trivial
>             Fix For: 3.0.0
>
>
> The explain output of the Hive CTAS command, regardless of whether it's actually writing via Hive's SerDe or converted into using Spark's data source, would always show that it's using {{InsertIntoHiveTable}} because it's hardcoded.
> e.g.
> {code:none}
> Execute OptimizedCreateHiveTableAsSelectCommand [Database:default, TableName: foo, InsertIntoHiveTable]
> {code}
> This CTAS is converted into using Spark's data source, but it still says {{InsertIntoHiveTable}} in the explain output.
> It's better to show the actual class name of the writing command used. For the example above, it'd be:
> {code:none}
> Execute OptimizedCreateHiveTableAsSelectCommand [Database:default, TableName: foo, InsertIntoHadoopFsRelationCommand]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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