imback82 opened a new pull request #25771: [SPARK-28970][SQL] Implement USE 
CATALOG/NAMESPACE for Data Source V2
URL: https://github.com/apache/spark/pull/25771
 
 
   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://spark.apache.org/contributing.html
     2. Ensure you have added or run the appropriate tests for your PR: 
https://spark.apache.org/developer-tools.html
     3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP][SPARK-XXXX] Your PR title ...'.
     4. Be sure to keep the PR description updated to reflect all changes.
     5. Please write your PR title to summarize what this PR proposes.
     6. If possible, provide a concise example to reproduce the issue for a 
faster review.
   -->
   
   ### What changes were proposed in this pull request?
   This PR exposes USE CATALOG/USE SQL commands as described in this 
[SPIP](https://docs.google.com/document/d/1jEcvomPiTc5GtB9F7d2RTVVpMY64Qy7INCA_rFEd9HQ/edit#)
   
   It also exposes `currentCatalog` in `CatalogManager`.
   
   Finally, it changes `SHOW NAMESPACES` and `SHOW TABLES` to use the current 
catalog if no catalog is specified (instead of default catalog).
   
   ### Why are the changes needed?
   There is currently no mechanism to change current catalog/namespace thru SQL 
commands.
   
   ### Does this PR introduce any user-facing change?
   Yes, you can perform the following:
   ```scala
   // Sets the current catalog to 'testcat'
   spark.sql("USE CATALOG testcat")
   
   // Sets the current catalog to 'testcat' and current namespace to 'ns1.ns2'.
   spark.sql("USE ns1.ns2 IN testcat")
   
   // Now, the following will use 'testcat' as the current catalog and 
'ns1.ns2' as the current namespace.
   spark.sql("SHOW NAMESPACES")
   ```
   
   ### How was this patch tested?
   Added new unit tests.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

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

Reply via email to