[
https://issues.apache.org/jira/browse/FLINK-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813215#comment-16813215
]
zhijiang commented on FLINK-6227:
---------------------------------
Exactly, this exception is received on consumer side via network stack and then
is {{setError}} on specific input channel. When this input channel is read by
task, it would {{checkError}} to interrupt task running. So the whole process
would not be through operator/user code to change this special 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)
