[
https://issues.apache.org/jira/browse/SPARK-29014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927796#comment-16927796
]
Wenchen Fan commented on SPARK-29014:
-------------------------------------
It doesn't require a major refactor but it's easier and cleaner to make this
change with a refactor that centralizes the catalog/table lookup logic.
> 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: [email protected]
For additional commands, e-mail: [email protected]
