[
https://issues.apache.org/jira/browse/FLINK-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323691#comment-17323691
]
Flink Jira Bot commented on FLINK-5089:
---------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Paris Carbone
> Priority: Major
> Labels: stale-assigned
>
> 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)
