You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/07/11 16:52:00 UTC
[jira] [Commented] (FLINK-12176) Unify JobGraph creation in
CliFrontend
[ https://issues.apache.org/jira/browse/FLINK-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883164#comment-16883164 ]
Till Rohrmann commented on FLINK-12176:
---------------------------------------
Yes exactly [~Tison]. I'm quite sure that there must an even older issue than FLINK-10879 describing this problem.
> Unify JobGraph creation in CliFrontend
> --------------------------------------
>
> Key: FLINK-12176
> URL: https://issues.apache.org/jira/browse/FLINK-12176
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client
> Affects Versions: 1.9.0
> Reporter: TisonKun
> Assignee: TisonKun
> Priority: Major
> Attachments: patch.diff
>
>
> Currently, we create {{JobGraph}} by the following process
> * if the cluster start in job mode, we create {{JobGraph}} by {{PackagedProgramUtils#createJobGraph}} and deploy a job cluster
> * if the cluster start in session mode, we create {{JobGraph}} and submit it by {{CliFrontend#executeProgram}}, which internally the same as above but using {{ContextEnvironment}} instead of {{OptimizerPlanEnvironment}}.
> {{ContextEnvironment}} not only create the job graph but also submit it. However, the processes of {{JobGraph}} creation in job mode and session mode are similar. That means, we can unify the process by always create {{JobGraph}} by {{PackagedProgramUtils#createJobGraph}}. And,
> * in job mode, deploy job cluster with the {{JobGraph}}
> * in session mode, submit the {{JobGraph}} to the session cluster
> From a higher view, it is helpful for a common view of job submission in both job and session mode and give opportunities to refactor legacy client codes.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)