Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.incubator.apache.org
Date: Tue, 22 Dec 2015 04:30:46 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@apex.incubator.apache.org
Message-ID: <JIRA.12919232.1440192012000.89707.1450758646692@Atlassian.JIRA>
In-Reply-To: <JIRA.12919232.1440192012000@Atlassian.JIRA>
References: <JIRA.12919232.1440192012000@Atlassian.JIRA>
 <JIRA.12919232.1440192012000@arcas>
Subject: [jira] [Commented] (APEXCORE-60) Iterative processing support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Github user gauravgopi123 commented on a diff in the pull request:

    https://github.com/apache/incubator-apex-core/pull/185#discussion_r48221148
  
    --- Diff: engine/src/test/java/com/datatorrent/stram/engine/GenericNodeTest.java ---
    @@ -277,6 +277,8 @@ public int getCount(boolean reset)
         gn.connectInputPort("ip1", reservoir1);
         gn.connectInputPort("ip2", reservoir2);
         gn.connectOutputPort("op", output);
    +    gn.firstWindowMillis = 0L;
    --- End diff --
    
    387 line has firstWindowMillis initialized as 0 and here firstWindowMillis is initialized as 0L. Can we use same format?


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