[
https://issues.apache.org/jira/browse/FLINK-14330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953889#comment-16953889
]
Till Rohrmann commented on FLINK-14330:
---------------------------------------
Sorry for taking so long to get back to you [~zhuzh]. I think your proposal
makes sense and the POC also looks good to me. Unifying the topology interfaces
could also help in the future with pipelined region based scheduling where the
SchedulingTopology would need to provide information about pipelined regions.
I've assigned you to this ticket.
> Introduce a unified topology interface
> --------------------------------------
>
> Key: FLINK-14330
> URL: https://issues.apache.org/jira/browse/FLINK-14330
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Fix For: 1.10.0
>
>
> When working on FLINK-14312 to partition {{JobGraph}} into logical pipelined
> regions, I found that we can hardly reuse the existing util
> {{PipelinedRegionComputeUtil#computePipelinedRegions(..)}} to do it since
> it's based on the {{FailoverTopology}}.
> To avoid code duplication, we need a unified topology base for
> {{FailoverTopology}} and {{JobGraph/LogicalTopology}}.
> Besides that, the inconsistency of {{FailoverTopology}} and
> {{SchedulingTopology}} is also causing troubles for development and
> performance.
> That's why I'd propose to unify the interfaces all these topologies. More
> details can be found in this [design
> doc|https://docs.google.com/document/d/1f88luAOfUQ6Pm4JkxYexLXpfH-crcXJdbubi1pS2Y5A/edit?usp=sharing].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
