[
https://issues.apache.org/jira/browse/FLINK-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902068#comment-16902068
]
Till Rohrmann commented on FLINK-13573:
---------------------------------------
I think you are right [~Tison]. The migration path should be to stop all
running jobs with the stop-with-savepoint command and then resuming them on the
new cluster. If we do this change, then we could add this to the release notes
of this issue (in case people run into serialization problems).
At the moment I cannot think about any problems this refactoring could entail.
However, I'm wondering what we gain apart from getting rid of a wrapper class.
> Merge SubmittedJobGraph into JobGraph
> -------------------------------------
>
> Key: FLINK-13573
> URL: https://issues.apache.org/jira/browse/FLINK-13573
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: TisonKun
> Priority: Major
> Fix For: 1.10.0
>
>
> As time goes on, {{SubmittedJobGraph}} becomes a thin wrapper of {{JobGraph}}
> without any additional information. It is reasonable that we merge
> {{SubmittedJobGraph}} into {{JobGraph}} and use only {{JobGraph}}.
> WDYT? cc [~till.rohrmann] [~GJL]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
