[
https://issues.apache.org/jira/browse/SPARK-58895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu Zhang updated SPARK-58895:
-------------------------------
Description:
Spark currently identifies `spark_catalog` as the session catalog and rewrites
its view commands
to V1 commands even when the configured implementation supports `ViewCatalog`.
This bypasses the
custom catalog's view implementation and makes commands such as `CREATE VIEW`,
`ALTER VIEW`,
`DROP VIEW`, and `SHOW VIEWS` behave inconsistently.
The dispatch needs to consider the catalog's view capability and the resolved
view payload so
native V2 views use the custom catalog while delegated V1 and temporary views
retain their
existing behavior.
> Route custom session view catalogs through V2 commands
> ------------------------------------------------------
>
> Key: SPARK-58895
> URL: https://issues.apache.org/jira/browse/SPARK-58895
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 5.0.0
> Reporter: Manu Zhang
> Priority: Major
> Labels: pull-request-available
>
> Spark currently identifies `spark_catalog` as the session catalog and
> rewrites its view commands
> to V1 commands even when the configured implementation supports
> `ViewCatalog`. This bypasses the
> custom catalog's view implementation and makes commands such as `CREATE
> VIEW`, `ALTER VIEW`,
> `DROP VIEW`, and `SHOW VIEWS` behave inconsistently.
> The dispatch needs to consider the catalog's view capability and the resolved
> view payload so
> native V2 views use the custom catalog while delegated V1 and temporary views
> retain their
> existing behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
