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/05/28 11:26: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: stale-major starter usability (was: starter usability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> 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
> Labels: stale-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)