You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Pramod Immaneni (JIRA)" <ji...@apache.org> on 2016/02/26 01:12:18 UTC

[jira] [Updated] (APEXCORE-360) Add capability in the engine to let the operator know about the next checkpoint window

     [ https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pramod Immaneni updated APEXCORE-360:
-------------------------------------
    Issue Type: Improvement  (was: Bug)

> Add capability in the engine to let the operator know about the next checkpoint window
> --------------------------------------------------------------------------------------
>
>                 Key: APEXCORE-360
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-360
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Pramod Immaneni
>            Assignee: Pramod Immaneni
>
> Carryover from the older JIRA system..
> The operator should be able to call an engine API to find out the number of windows till the next checkpoint.
> Implementation of iteration feature requires the need to know the number of windows from checkpoint. If the delay is 1 the delay operator needs to know about the window before checkpoint by beginWindow of that window so it can save the tuples in that window for replay in case of recovery in future. If the delay is 2 then it needs to know 2 windows before checkpoint.
> The idea is to compute the windows from checkpoint and make it available in OperatorContext, for example by a method getWindowsFromCheckpoint. The operator can check the windows from checkpoint in beginWindow. In the iteration case it can save the tuples accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)