[
https://issues.apache.org/jira/browse/FLINK-13041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek closed FLINK-13041.
------------------------------------
Resolution: Won't Do
Won't do it in the end in, we'll do FLINK-12961
> Make ScheduleMode configurable on ExecutionConfig
> -------------------------------------------------
>
> Key: FLINK-13041
> URL: https://issues.apache.org/jira/browse/FLINK-13041
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The new Blink-based Table API Runner currently needs a way of globally
> setting the {{ScheduleMode}} (either {{LAZY_FROM_SOURCES}} or {{EAGER}}) to
> support both batch-style and streaming-style execution.
> This is a stop-gap solution. Ideally, {{Transformations}} would know whether
> they are bounded or not and the scheduler could decide the scheduling mode
> based on that information but this requires more work on both the Table API
> Runner and the DAG API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
