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 2021/01/08 15:42:01 UTC

[jira] [Updated] (FLINK-20903) Remove SchedulerNG.initialize method

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

Till Rohrmann updated FLINK-20903:
----------------------------------
    Description: 
The {{SchedulerNG}} no longer needs the {{initialize}} method because the {{JobMaster}} is now started with a valid {{MainThreadExecutor}}. Hence, we can simplify the {{SchedulerNG}} by passing the {{ComponentMainThreadExecutor}} to the constructor of the implementations.

Similarly, we can remove the {{SchedulerNG.registerJobStatusListener}} method.

  was:The {{SchedulerNG}} no longer needs the {{initialize}} method because the {{JobMaster}} is now started with a valid {{MainThreadExecutor}}. Hence, we can simplify the {{SchedulerNG}} by passing the {{ComponentMainThreadExecutor}} to the constructor of the implementations.


> Remove SchedulerNG.initialize method
> ------------------------------------
>
>                 Key: FLINK-20903
>                 URL: https://issues.apache.org/jira/browse/FLINK-20903
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.13.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>             Fix For: 1.13.0
>
>
> The {{SchedulerNG}} no longer needs the {{initialize}} method because the {{JobMaster}} is now started with a valid {{MainThreadExecutor}}. Hence, we can simplify the {{SchedulerNG}} by passing the {{ComponentMainThreadExecutor}} to the constructor of the implementations.
> Similarly, we can remove the {{SchedulerNG.registerJobStatusListener}} method.



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