You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Terry Kim (Jira)" <ji...@apache.org> on 2019/09/10 03:52:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16926307#comment-16926307 ]
Terry Kim commented on SPARK-29014:
-----------------------------------
[~rdblue] / [~cloud_fan] did you start working on it? If not, I can take this. Please let me know.
> 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
> Priority: Blocker
>
> 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.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org