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 2022/02/11 01:19:00 UTC

[jira] [Closed] (FLINK-25996) Introduce job property isDynamicGraph to ExecutionConfig

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

Zhu Zhu closed FLINK-25996.
---------------------------
    Resolution: Done

master/release-1.15:
90159f4c7f364f9264e0373c0b1ffa7cafa04cbc

> Introduce job property isDynamicGraph to ExecutionConfig
> --------------------------------------------------------
>
>                 Key: FLINK-25996
>                 URL: https://issues.apache.org/jira/browse/FLINK-25996
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Zhu Zhu
>            Assignee: Lijie Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> To enable FLINK-25995 and FLINK-25046 only in dynamic graph scenario, we need a property ExecutionConfig#isDynamicGraph. 
> In the first step, it should be an internal property that we do not want users to get/set. The property will be decided automatically, true iff config {{jobmanager.scheduler}} is {{AdaptiveBatch}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)