[
https://issues.apache.org/jira/browse/FLINK-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kostas Kloudas closed FLINK-19392.
----------------------------------
Resolution: Implemented
Merged on master with c2e3399200010527e06e698b191bd5290f1d2ce4 and
14954490598863d2ede22eaac0282d90d206431e
> Detect the execution mode based on the sources in the job.
> ----------------------------------------------------------
>
> Key: FLINK-19392
> URL: https://issues.apache.org/jira/browse/FLINK-19392
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataStream
> Affects Versions: 1.12.0
> Reporter: Kostas Kloudas
> Assignee: Kostas Kloudas
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> As part of FLIP-134, we introduce the option {{execution.runtime-mode}} which
> can take the values: BATCH, STREAMING, and AUTOMATIC.
> In case of the latter, the system will scan the sources and detect if the job
> is to be execute either using batch scheduling or streaming. If all the
> sources are bounded, the system will go with BATCH, if at least one is
> unbounded, then the system will go with STREAMING.
> This issue targets introducing the logic of detecting the runtime mode based
> on the sources without exposing it yet to the user. The latter will happen in
> a follow-up issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
