[
https://issues.apache.org/jira/browse/SPARK-60625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uroš Bojanić resolved SPARK-60625.
----------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
Issue resolved by pull request 59869
[https://github.com/apache/spark/pull/59869]
> Separate session-catalog SHOW goldens from V2 catalog coverage
> --------------------------------------------------------------
>
> Key: SPARK-60625
> URL: https://issues.apache.org/jira/browse/SPARK-60625
> Project: Spark
> Issue Type: Test
> Components: SQL
> Affects Versions: 4.4.0
> Reporter: Vladan Vasić
> Assignee: Vladan Vasić
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.4.0
>
>
> Follow up to SPARK-60583.
> The show-commands.sql golden input mixes session-catalog SHOW behavior with
> custom InMemoryCatalog setup and nested V2 namespace operations. It also
> hardcodes spark_catalog.default during cleanup even though the database was
> created in the current catalog.
> Keep the SQL golden focused on session-catalog SHOW results, schemas and
> analyzed command nodes. Return to the current catalog's default namespace
> before dropping the test database.
> Extend the existing DataSourceV2SQLSuite tests to retain the custom-catalog
> coverage: catalog loading, case-insensitive wildcard matching, patterns
> without LIKE, no-match patterns, empty and multipart namespaces, quoted
> namespace components, and the CURRENT DATABASE / CURRENT SCHEMA aliases.
> Regenerate the execution-result and analyzed-plan goldens and verify both
> golden tests plus the affected V2 tests.
> No production behavior changes.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
