[ 
https://issues.apache.org/jira/browse/SPARK-61470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyukjin Kwon resolved SPARK-61470.
----------------------------------
    Resolution: Fixed

Issue resolved by pull request 535
[https://github.com/apache/spark-connect-rust/pull/535]

> Let Ctrl-C end every call of the Python client that waits for the server, and 
> raise the error of a failed interrupt, as PySpark does
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-61470
>                 URL: https://issues.apache.org/jira/browse/SPARK-61470
>             Project: Spark
>          Issue Type: Bug
>          Components: Connect
>    Affects Versions: connect-rust-4.3.0
>            Reporter: Hyukjin Kwon
>            Assignee: Hyukjin Kwon
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: connect-rust-4.3.0
>
>
> Follow-up of SPARK-61407. spark.conf.get/set, DataFrame.schema/columns, 
> interruptAll/interruptTag/interruptOperation, addArtifacts, cloneSession and 
> the RustConnectStub calls wait for the server with a bare py.detach, so 
> Ctrl-C does not end them against a hung or unreachable server, where PySpark 
> raises KeyboardInterrupt at once. When the Interrupt that a Ctrl-C sends 
> fails, the drop-in drops its error, and a held toLocalIterator then ignores 
> the first Ctrl-C; PySpark raises the error of the interrupt, with the 
> KeyboardInterrupt as its context.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

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

Reply via email to