hvanhovell opened a new pull request, #48687:
URL: https://github.com/apache/spark/pull/48687

   ### What changes were proposed in this pull request?
   This PR makes the following changes:
   - It adds shims for a couple of a number of classes exposed in the (classic) 
SQL interface:  `BaseRelation` , `ExperimentalMethods`, 
`ExecutionListenerManager`, `SharedState`, `SessionState`, `SparkConf`, 
`SparkSessionExtensions`, `QueryExecution`, and `SQLContext`.
   - It adds all public methods involving these classes. For classic they will 
just work like before. For connect they will throw 
`SparkUnsupportedOperationExceptions` when used.
   - It reduces the visibility of a couple of classes added recently: 
`DataSourceRegistration`, and `UDTFRegistration`.
   - I have also reorganized all the shims into a single class.
   
   Please note that this is by no means reflects the final state. We do intent 
to support `SQLContext`. We also are thinking about removing 
`ExperimentalMethods`, `SharedState`, `SessionState` from the public interface. 
For `QueryExecution`, and `ExecutionListenerManager` we are considering adding 
a plan representation similar that is not tied to catalyst.
   
   ### Why are the changes needed?
   We are creating a shared Scala (JVM) SQL interface for both Classic and 
Connect.
   
   ### Does this PR introduce _any_ user-facing change?
   It adds unusable public methods to the connect interface.
   
   ### How was this patch tested?
   I have added tests that checks if the connect client throws the proper 
exceptions.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   No.


-- 
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