You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2020/02/25 12:30:00 UTC
[jira] [Updated] (FLINK-16276) Introduce factory methods to create
DefaultScheduler for testing
[ https://issues.apache.org/jira/browse/FLINK-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu updated FLINK-16276:
----------------------------
Parent: (was: FLINK-10429)
Issue Type: Task (was: Sub-task)
> Introduce factory methods to create DefaultScheduler for testing
> ----------------------------------------------------------------
>
> Key: FLINK-16276
> URL: https://issues.apache.org/jira/browse/FLINK-16276
> Project: Flink
> Issue Type: Task
> Components: Runtime / Coordination, Tests
> Affects Versions: 1.11.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Fix For: 1.11.0
>
>
> Currently tests create DefaultScheduler via its constructor. Having a builder and a set of factory methods can significantly reduce the complexity to instantiate DefaultScheduler.
> It can be very helpful especially when we are to rework tests to base on the new scheduler.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)