You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2022/01/15 10:15:00 UTC

[jira] [Closed] (FLINK-10804) Transfer suppressed exceptions with SerializedThrowable

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

Till Rohrmann closed FLINK-10804.
---------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

Fixed via 99a101ca0916d4dc90dcaebce16bf68b3895e548

> Transfer suppressed exceptions with SerializedThrowable
> -------------------------------------------------------
>
>                 Key: FLINK-10804
>                 URL: https://issues.apache.org/jira/browse/FLINK-10804
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.7.0, 1.10.2, 1.11.2
>            Reporter: Nico Kruber
>            Assignee: Kirill Listopad
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available, starter, usability
>             Fix For: 1.15.0
>
>
> Currently, {{SerializedThrowable}} mimics the original exception including the causes but not the suppressed exceptions. You may argue whether these should really be transferred as well or whether it would be enough to have them in the logging of the component which sent the message.
> However, it may be surprising to silently drop suppressed exceptions.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)