You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kostas Kloudas (Jira)" <ji...@apache.org> on 2020/04/21 09:21:00 UTC

[jira] [Closed] (FLINK-16658) Wire the EmbeddedExecutor to the StandaloneJobClusterEntryPoint.

     [ https://issues.apache.org/jira/browse/FLINK-16658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kostas Kloudas closed FLINK-16658.
----------------------------------
    Resolution: Implemented

Merged on master with 74fc5a7cc8132eec2a247f6894a81a63a1e6128a

> Wire the EmbeddedExecutor to the StandaloneJobClusterEntryPoint.
> ----------------------------------------------------------------
>
>                 Key: FLINK-16658
>                 URL: https://issues.apache.org/jira/browse/FLINK-16658
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Job Execution / Application Mode
>    Affects Versions: 1.10.0
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> This will replace the current logic of job execution in the {{StandaloneJobClusterEntryPoint}} with one that uses the newly introduced {{EmbeddedExecutor}}.
> Currently, the {{ClassPathJobGraphRetriever}} is the one that "discovers" the user's main in the classpath of the JobMaster, and it extracts the {{JobGraph}} from that using the {{PackagedProgramUtils}} which highjack the {{env.execute()}} method. With this change, we will actually run the {{main()}} on the {{JobMaster}}, conceptually, the same way we execute user programs from the CLI.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)