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

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

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

> Keep the replaced error as the context of the done error of a progress 
> handler, as PySpark does
> -----------------------------------------------------------------------------------------------
>
>                 Key: SPARK-61398
>                 URL: https://issues.apache.org/jira/browse/SPARK-61398
>             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
>
>
> A follow-up of SPARK-61342, found in a post-merge review. When the done call 
> of a progress handler raises after the execution failed, PySpark raises the 
> handler's error with the execution's error as __context__; the drop-in drops 
> the execution's error, so __context__ is None. For an iterator dropped before 
> its end, the error is reported to sys.unraisablehook with no object, so the 
> 'Exception ignored in' header that PySpark prints is missing.



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