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 2019/04/09 09:57:00 UTC
[jira] [Commented] (FLINK-6227) Introduce the
DataConsumptionException for downstream task failure
[ https://issues.apache.org/jira/browse/FLINK-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813203#comment-16813203 ]
Till Rohrmann commented on FLINK-6227:
--------------------------------------
Thanks for taking on this issue [~zjwang]. The important bit is that the resulting exception must not be passed through the user code because it could potentially catch and change the exception.
> Introduce the DataConsumptionException for downstream task failure
> ------------------------------------------------------------------
>
> Key: FLINK-6227
> URL: https://issues.apache.org/jira/browse/FLINK-6227
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Network
> Reporter: zhijiang
> Assignee: zhijiang
> Priority: Minor
>
> It is part of FLIP-1.
> We define a new special exception to indicate the downstream task failure in consuming upstream data.
> The {{JobManager}} will receive and consider this special exception to calculate the minimum connected sub-graph which is called {{FailoverRegion}}. So the {{DataConsumptionException}} should contain {{ResultPartitionID}} information for {{JobMaster}} tracking upstream executions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)