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 2019/09/26 04:08:00 UTC
[jira] [Updated] (FLINK-14059) Introduce option
allSourcesInSamePipelinedRegion in ExecutionConfig
[ https://issues.apache.org/jira/browse/FLINK-14059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu updated FLINK-14059:
----------------------------
Component/s: Table SQL / Runtime
Runtime / Coordination
> Introduce option allSourcesInSamePipelinedRegion in ExecutionConfig
> -------------------------------------------------------------------
>
> Key: FLINK-14059
> URL: https://issues.apache.org/jira/browse/FLINK-14059
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination, Table SQL / Runtime
> Affects Versions: 1.10.0
> Reporter: Xintong Song
> Assignee: Zhu Zhu
> Priority: Major
> Fix For: 1.10.0
>
>
> * Introduce option {{allSourcesInSamePipelinedRegion}} in {{ExecutionConfig}}
> * Set it to {{true}} by default
> * Set it to {{false}} for SQL/Table API bounded batch jobs by the Blink planner
> This step should not introduce any behavior changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)