[
https://issues.apache.org/jira/browse/FLINK-36446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888639#comment-17888639
]
david radley commented on FLINK-36446:
--------------------------------------
[~JunRuiLi] I do not know this area well. I see that JobGraph is mentioned in
[https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/overview/#overview-and-reference-architecture|http://example.com/]where
it says: _It takes the code of the Flink applications, transforms it into a
JobGraph and submits it to the JobManager._
I see
[https://nightlies.apache.org/flink/flink-docs-master/docs/internals/job_scheduling/#jobmanager-data-structures|http://example.com/]
where it says : _The JobManager transforms the JobGraph into an
[ExecutionGraph|https://github.com/apache/flink/blob/master//flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/]_
I am curious if the ExecutionPlan is transformed into an ExecutionGraph, after
this fix, what is the role of the JobGraph class, which I did not see deleted
by this fix.
> Refactor Job Submission Process to Use ExecutionPlan Instead of JobGraph
> ------------------------------------------------------------------------
>
> Key: FLINK-36446
> URL: https://issues.apache.org/jira/browse/FLINK-36446
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Junrui Li
> Assignee: Junrui Li
> Priority: Major
> Labels: pull-request-available
>
> Refactor the job submission process to submit an {{ExecutionPlan}} instead of
> a {{{}JobGraph{}}}.
> Since {{JobGraph}} implements the {{ExecutionPlan}} interface, this change
> will not impact the existing submission process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
