[
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 (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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
>
> 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.3.4#803005)
