[
https://issues.apache.org/jira/browse/FLINK-14510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-14510:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Remove the lazy vertex attaching mechanism from ExecutionGraph
> --------------------------------------------------------------
>
> Key: FLINK-14510
> URL: https://issues.apache.org/jira/browse/FLINK-14510
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> Currently in production, the vertex attaching is only invoked right after the
> ExecutionGraph is created in ExecutionGraphBuilder. That means lazy attaching
> is not necessary at the moment. It however adds extra complexity to
> ExecutionGraph, since we need to assume that the vertices may be not
> initialized or even get changed.
> Moreover, attaching vertices after a job starts scheduling is an undefined
> behavior which would not work properly.
> I'd propose to remove the lazy attaching mechanism, and do vertices building
> and related components initialization in ExecutionGraph constructor.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
