[ https://issues.apache.org/jira/browse/FLINK-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-18295: ----------------------------------- Labels: auto-unassigned stale-major (was: auto-unassigned) 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. > Remove the hack logics of result consumers > ------------------------------------------ > > Key: FLINK-18295 > URL: https://issues.apache.org/jira/browse/FLINK-18295 > Project: Flink > Issue Type: Technical Debt > Components: Runtime / Coordination > Reporter: Zhu Zhu > Priority: Major > Labels: auto-unassigned, stale-major > > 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)