You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/04/10 10:39:00 UTC
[jira] [Updated] (FLINK-14521) CoLocationGroup is not set into JobVertex if the stream node is chained with others
[ https://issues.apache.org/jira/browse/FLINK-14521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-14521:
-----------------------------------
Labels: auto-deprioritized-major pull-request-available stale-minor (was: auto-deprioritized-major pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> CoLocationGroup is not set into JobVertex if the stream node is chained with others
> -----------------------------------------------------------------------------------
>
> Key: FLINK-14521
> URL: https://issues.apache.org/jira/browse/FLINK-14521
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.9.0, 1.9.1
> Reporter: Yun Gao
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available, stale-minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> StreamingJobGraphGenerator.isChainable dose not consider the coLocationGroup, if A -> B is chained, the coLocationGroup of the corresponding JobVertex will be set with that of the head node, namely A. Therefore, if B has declared coLocationGroup but A does not, then the coLocationGroup of B will be ignored.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)