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

Posted to issues@flink.apache.org by "Matthias (Jira)" <ji...@apache.org> on 2020/09/25 11:01:00 UTC

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

    [ https://issues.apache.org/jira/browse/FLINK-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202059#comment-17202059 ] 

Matthias edited comment on FLINK-10804 at 9/25/20, 11:00 AM:
-------------------------------------------------------------

This issue was revisited as part of the Engine team's backlog grooming on Sep 25, 2020. It was still considered a valid improvement.


was (Author: mapohl):
This issue was revisited as part of the Engine team's backlog grooming on Sep 25, 2020.

> 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
>            Priority: Major
>
> 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.3.4#803005)