You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2018/07/12 07:46:00 UTC
[jira] [Resolved] (FLINK-9809) Support setting CoLocation
constraints on the DataStream Transformations
[ https://issues.apache.org/jira/browse/FLINK-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-9809.
---------------------------------
Resolution: Fixed
Implemented in 3f0b9fee5185fcc7200179459bed31fb4bd08bbf
> Support setting CoLocation constraints on the DataStream Transformations
> ------------------------------------------------------------------------
>
> Key: FLINK-9809
> URL: https://issues.apache.org/jira/browse/FLINK-9809
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> Flink supports co location constraints for operator placement during scheduling. This is used internally for iterations, for example, but is not exposed to users.
> I propose to add a way for expert users to set these constraints. As a first step, I would add them to the {{StreamTransformation}}, which is not part of the public user-facing classes, but a more internal class in the DataStream API. That way we make this initially a hidden feature and can gradually expose it more prominently when we agree that this would be a good idea.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)