[
https://issues.apache.org/jira/browse/APEXCORE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113525#comment-15113525
]
ASF GitHub Bot commented on APEXCORE-60:
----------------------------------------
GitHub user davidyan74 opened a pull request:
https://github.com/apache/incubator-apex-core/pull/211
APEXCORE-60 Iteration support in Apex Core (rebased)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davidyan74/incubator-apex-core
APEXCORE-60-rebased
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-core/pull/211.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #211
----
commit f7e1ccf14154eca92b24c5f6b5387fe56c516829
Author: David Yan <[email protected]>
Date: 2015-12-09T23:52:26Z
APEXCORE-60 Iteration support in Apex Core
commit 4d5828c6ca48f5d28cd8c77c5706c6f72c7cd1ad
Author: Gaurav <[email protected]>
Date: 2015-12-16T14:33:54Z
moved attribute from context to logical plan
commit b3402be5a45728515f4a8328fec5a76ddede0350
Author: Thomas Weise <[email protected]>
Date: 2016-01-22T00:39:55Z
APEXCORE-306 Update checkpoints for strongly connected operators as group.
----
> Iterative processing support
> ----------------------------
>
> Key: APEXCORE-60
> URL: https://issues.apache.org/jira/browse/APEXCORE-60
> Project: Apache Apex Core
> Issue Type: New Feature
> Reporter: David Yan
> Assignee: David Yan
> Labels: roadmap
> Fix For: 3.3.0
>
>
> We would like to support iterative processing by introducing cycles in the
> graph (known as DAG now, but no longer if we support iterative processing).
> Initial idea is as follow:
> {noformat}
> |----|
> v |
> A -> B -> C -> D
> ^ |
> |---------|
> {noformat}
> C has two separate backward streams to A and B. The input ports of A and B
> that C connects to will have a special attribute on how many window IDs ahead
> the incoming windows should be treated as, and A and B will be responsible
> for the initial data for such input ports.
> Another idea is to have C advance the window ID on its output ports and have
> C generate the initial data on its output ports to A and B.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
