Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.5.0
-
None
Description
Currently SparkConnect only validates that the server-side session is the same on the client side, during the receipt of the response from the server. This allow that the sparkconnect server executes the command on the wrong spark session, which can succeed, and the client will bail-out only when it get the response back.
Attachments
Issue Links
- is cloned by
-
SPARK-47708 Do not log the gRPC exception to stderr in PySpark
- Resolved
- links to