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 2021/01/07 11:54:01 UTC
[jira] [Commented] (FLINK-20850) Analyze whether
CoLocationConstraints and CoLocationGroup can be removed
[ https://issues.apache.org/jira/browse/FLINK-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260456#comment-17260456 ]
Zhu Zhu commented on FLINK-20850:
---------------------------------
Agreed that `CoLocationConstraint` is no longer needed after `SchedulerImpl` is removed.
But I think `CoLocationGroup` is still needed in graph building because `CoLocationGroupDesc` is a read-only version. However, it can be simplified by removing the `CoLocationConstraint` related methods.
> Analyze whether CoLocationConstraints and CoLocationGroup can be removed
> ------------------------------------------------------------------------
>
> Key: FLINK-20850
> URL: https://issues.apache.org/jira/browse/FLINK-20850
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Matthias
> Priority: Major
>
> It appears that {{CoLocationGroup}} and {{CoLocationContraint}} are not used by {{LocalInputPreferredSlotSharingStrategy}} anymore. Instead, {{CoLocationGroupDesc}} and {{CoLocationContraintDesc}} serve as light-weight versions of these concepts.
> Does this mean that we can remove the former ones?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)