[
https://issues.apache.org/jira/browse/FLINK-14059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967381#comment-16967381
]
Zhu Zhu commented on FLINK-14059:
---------------------------------
Agreed that we should put it into StreamGraph if it is for internal use only
[~dwysakowicz]. We just had a similar discussion on it [here|
https://github.com/apache/flink/pull/10007#discussion_r342111903].
One thing I'm not sure is that whether in the future we should make this
configuration open to users to customize this strategy. For example, one can
force streaming job regions to be in different slot sharing groups by default.
If we are sure not to, then I'd be fine to move it into StreamGraph.
> Introduce option allVerticesInSameSlotSharingGroupByDefault 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
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Introduce option -{{allSourcesInSamePipelinedRegion}}-
> {{allVerticesInSameSlotSharingGroupByDefault}} 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)
