[jira] [Created] (FLINK-18295) Remove the hack logics of result consumers

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-18295) Remove the hack logics of result consumers

Shang Yuanchun (Jira)
Zhu Zhu created FLINK-18295:
-------------------------------

             Summary: 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
             Fix For: 1.12.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)