Return-Path: X-Original-To: apmail-apex-dev-archive@minotaur.apache.org Delivered-To: apmail-apex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F1A3118765 for ; Mon, 4 Jan 2016 20:35:50 +0000 (UTC) Received: (qmail 87136 invoked by uid 500); 4 Jan 2016 20:35:50 -0000 Delivered-To: apmail-apex-dev-archive@apex.apache.org Received: (qmail 87080 invoked by uid 500); 4 Jan 2016 20:35:50 -0000 Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.incubator.apache.org Delivered-To: mailing list dev@apex.incubator.apache.org Received: (qmail 87069 invoked by uid 99); 4 Jan 2016 20:35:50 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jan 2016 20:35:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 4D054C023A for ; Mon, 4 Jan 2016 20:35:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.427 X-Spam-Level: X-Spam-Status: No, score=0.427 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.554, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id bxDlPCojd00F for ; Mon, 4 Jan 2016 20:35:41 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id DA293258CE for ; Mon, 4 Jan 2016 20:35:40 +0000 (UTC) Received: (qmail 85854 invoked by uid 99); 4 Jan 2016 20:35:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jan 2016 20:35:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id ECC262C1F68 for ; Mon, 4 Jan 2016 20:35:39 +0000 (UTC) Date: Mon, 4 Jan 2016 20:35:39 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (APEXCORE-60) Iterative processing support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/APEXCORE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081755#comment-15081755 ] 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_r48777786 --- Diff: engine/src/main/java/com/datatorrent/stram/engine/GenericNode.java --- @@ -343,12 +389,15 @@ else if (!doCheckpoint) { * we will receive tuples which are equal to the number of input streams. */ activePort.remove(); - buffers.remove(); + if (isInputPortConnectedToDelayOperator(activePortEntry.getKey())) { + break; // breaking out of the switch/case + } + buffers.remove(); --- End diff -- Should this not be before `if` condition above? > 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)