[
https://issues.apache.org/jira/browse/FLINK-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5089:
----------------------------------
Labels: auto-deprioritized-major auto-unassigned stale-minor (was:
auto-deprioritized-major auto-unassigned)
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.
> Introduce Loop functions and Enforce Nesting on Data Streams
> ------------------------------------------------------------
>
> Key: FLINK-5089
> URL: https://issues.apache.org/jira/browse/FLINK-5089
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Reporter: Paris Carbone
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, stale-minor
>
> The current programming model of stream iterations in the DataStream API is
> exposed through low-level dataflow operations for placing arbitrary
> feedback-edges. This strategy does not enforce proper nesting and requires
> user-defined timeouts to enforce termination. It further impacts correctness,
> resulting to incomplete processing or/and inconsistent state when iterations
> exist in the topology. There is a need for a new functional, yet
> compositional API (i.e. nested loops) for expressing asynchronous DataStream
> loops to be able to build easily decentralized progress establishment
> algorithms such as distributed termination and parallel structured or
> fixpoint iterations.
> This Jira explains parts of the needs addressed by FLIP-15 on Loops and
> Terminations.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
