vladanvasi-db opened a new pull request, #59835:
URL: https://github.com/apache/spark/pull/59835

   ### What changes were proposed in this pull request?
   
   Add one `show-commands.sql` input with execution-result and analyzed-plan 
goldens for:
   
   - `SHOW CATALOGS`: catalog loading, case-insensitive wildcard filtering and 
no matches.
   - `SHOW CURRENT NAMESPACE`: session catalog and V2 namespace state, an empty 
namespace,
     quoted multipart namespaces, and the `CURRENT DATABASE` / `CURRENT SCHEMA` 
aliases.
   - `SHOW COLLATIONS`: a bounded UTF8/ICU selection, an exact pattern without 
`LIKE`,
     and no matches.
   
   The input contains 11 SHOW scenarios plus setup and cleanup statements. No 
production
   code changes.
   
   ### Why are the changes needed?
   
   Tracks [SPARK-60583](https://issues.apache.org/jira/browse/SPARK-60583).
   
   Keep command outputs, output schemas and analyzed command nodes covered 
together in
   `SQLQueryTestSuite`. A small collation selection avoids snapshotting the 
entire ICU inventory.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   Regenerated both golden files with `SPARK_GENERATE_GOLDEN_FILES=1`, then 
reran without
   regeneration:
   
   ```bash
   build/sbt 'sql/testOnly org.apache.spark.sql.SQLQueryTestSuite -- -z 
show-commands.sql'
   ```
   
   Both `show-commands.sql` and `show-commands.sql_analyzer_test` passed (2 
tests, 0 failures).
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: OpenAI Codex CLI 0.164.0
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to