[
https://issues.apache.org/jira/browse/FLINK-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322998#comment-17322998
]
Flink Jira Bot commented on FLINK-18295:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Remove the hack logics of result consumers
> ------------------------------------------
>
> Key: FLINK-18295
> URL: https://issues.apache.org/jira/browse/FLINK-18295
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: stale-assigned
> Fix For: 1.13.0
>
>
> Currently an {{IntermediateDataSet}} can have multiple {{JobVertex}} as its
> consumers. That's why the consumers of a `IntermediateResultPartition` is in
> the form of {{List<List<ExecutionEdge>>}}.
> However, in scheduler/{{ExecutionGraph}} there is assumption that one
> `IntermediateResultPartition` can be consumed by one only
> `ExecutionJobVertex`. This results in a lot of hack logics which assumes
> partition consumers to contain a single list.
> We should remove these hack logics. The idea is to change
> `IntermediateResultPartition#consumers` to be `List<ExecutionEdge>`.
> `ExecutionGraph` building logics should be adjusted accordingly with the
> assumption that an `IntermediateResult` can have one only consumer vertex. In
> `JobGraph`, there should also be check logics for this assumption.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
