apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-60) Iterative processing support
Date Sat, 23 Jan 2016 09:02:39 GMT

    [ https://issues.apache.org/jira/browse/APEXCORE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113654#comment-15113654
] 

ASF GitHub Bot commented on APEXCORE-60:
----------------------------------------

GitHub user tweise opened a pull request:

    https://github.com/apache/incubator-apex-core/pull/213

    APEXCORE-60 Isolate test checkpoint directories.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tweise/incubator-apex-core devel-3

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-apex-core/pull/213.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 #213
    
----
commit 50b0855d840eb99d03cf8877e4b208e9a0ec85f1
Author: Thomas Weise <thomas@datatorrent.com>
Date:   2016-01-23T09:00:29Z

    APEXCORE-60 Isolate test checkpoint directories.

----


> 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)

Mime
View raw message