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 2019/10/18 14:49:11 UTC

[jira] [Resolved] (SPARK-29014) DataSourceV2: Clean up current, default, and session catalog uses

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

Wenchen Fan resolved SPARK-29014.
---------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

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

> DataSourceV2: Clean up current, default, and session catalog uses
> -----------------------------------------------------------------
>
>                 Key: SPARK-29014
>                 URL: https://issues.apache.org/jira/browse/SPARK-29014
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Ryan Blue
>            Assignee: Terry Kim
>            Priority: Blocker
>             Fix For: 3.0.0
>
>
> Catalog tracking in DSv2 has evolved since the initial changes went in. We need to make sure that handling is consistent across plans using the latest rules:
>  * The _current_ catalog should be used when no catalog is specified
>  * The _default_ catalog is the catalog _current_ is initialized to
>  * If the _default_ catalog is not set, then it is the built-in Spark session catalog, which will be called `spark_catalog` (This is the v2 session catalog)



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