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 2021/10/28 10:41:01 UTC
[jira] [Updated] (FLINK-21392) Support to block in connected
streams
[ https://issues.apache.org/jira/browse/FLINK-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-21392:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was: auto-deprioritized-major)
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.
> Support to block in connected streams
> -------------------------------------
>
> Key: FLINK-21392
> URL: https://issues.apache.org/jira/browse/FLINK-21392
> Project: Flink
> Issue Type: New Feature
> Components: API / DataStream
> Reporter: Timo Walther
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> In many scenarios that involve control streams when using connected streams, users would like to wait until stream A is "ready" before processing the stream B.
> Internally we already provide input selectable semantics but with problems around checkpointing. Once those problems are solved, we should expose this functionality in the main API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)