You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Ryan Blue (JIRA)" <ji...@apache.org> on 2019/06/05 22:20:00 UTC

[jira] [Updated] (SPARK-27919) DataSourceV2: Add v2 session catalog

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

Ryan Blue updated SPARK-27919:
------------------------------
    Affects Version/s:     (was: 2.4.3)
                       3.0.0

> DataSourceV2: Add v2 session catalog
> ------------------------------------
>
>                 Key: SPARK-27919
>                 URL: https://issues.apache.org/jira/browse/SPARK-27919
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Ryan Blue
>            Priority: Major
>
> When no default catalog is set, the session catalog (v1) is responsible for table identifiers with no catalog part. When CTAS creates a table with a v2 provider, a v2 catalog is required and the default catalog is used. But this may cause Spark to create a table in a catalog that it cannot use to look up the table.
> In this case, a v2 catalog that delegates to the session catalog should be used instead.



--
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