You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/02/01 23:37:03 UTC
[jira] [Updated] (SPARK-30567) setDelegateCatalog should be called
if catalog has implemented CatalogExtension
[ https://issues.apache.org/jira/browse/SPARK-30567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-30567:
----------------------------------
Target Version/s: 3.1.0
> setDelegateCatalog should be called if catalog has implemented CatalogExtension
> -------------------------------------------------------------------------------
>
> Key: SPARK-30567
> URL: https://issues.apache.org/jira/browse/SPARK-30567
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: yu jiantao
> Priority: Major
> Fix For: 3.0.0
>
>
> CatalogManager.catalog calls Catalogs.load to load a catalog if it is not 'spark_catalog' . If the catalog has implemented CatalogExtension, setDelegateCatalog is not called when the catalog is loaded, which is not like that we have done for v2SessionCatalog, and that makes a confusion for customized session catalog, like iceberg SparkSessionCatalog.
--
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