You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/05 10:55:03 UTC

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

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

Flink Jira Bot updated FLINK-10804:
-----------------------------------
      Labels: auto-deprioritized-major starter usability  (was: stale-major starter usability)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> 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: Minor
>              Labels: auto-deprioritized-major, starter, usability
>
> 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)