[
https://issues.apache.org/jira/browse/APEXCORE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081691#comment-15081691
]
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_r48774037
--- Diff:
engine/src/main/java/com/datatorrent/stram/engine/GenericNode.java ---
@@ -394,6 +463,15 @@ else if (tracker.ports[trackerIndex] == activePort) {
case END_STREAM:
activePort.remove();
buffers.remove();
+ if (firstWindowId == -1) {
+ // this is for recovery from a checkpoint for
DelayOperator
+ if (delay) {
+ // if it's a DelayOperator and this is the first
RESET_WINDOW (start) or END_STREAM (recovery),
+ // fabricate the first window
+ fabricateFirstWindow((Operator.DelayOperator)operator,
windowAhead);
+ }
+ firstWindowId = t.getWindowId();
--- End diff --
Again same Should this firstWindowId not be assigned when delay is true and
firstWindowId == -1?
> 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)
