Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 08CF7200C66 for ; Sat, 15 Apr 2017 17:23:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 07801160B9D; Sat, 15 Apr 2017 15:23:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4CCD8160BA0 for ; Sat, 15 Apr 2017 17:23:46 +0200 (CEST) Received: (qmail 42046 invoked by uid 500); 15 Apr 2017 15:23:45 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 42022 invoked by uid 99); 15 Apr 2017 15:23:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Apr 2017 15:23:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 17C51180688 for ; Sat, 15 Apr 2017 15:23:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Z8LOgWM61rIa for ; Sat, 15 Apr 2017 15:23:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AFCDC5FBE5 for ; Sat, 15 Apr 2017 15:23:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E2076E00A6 for ; Sat, 15 Apr 2017 15:23:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 499CE20D59 for ; Sat, 15 Apr 2017 15:23:42 +0000 (UTC) Date: Sat, 15 Apr 2017 15:23:41 +0000 (UTC) From: "Pramod Immaneni (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (APEXCORE-360) Add capability in the engine to let the operator know about the next checkpoint window MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 15 Apr 2017 15:23:47 -0000 [ https://issues.apache.org/jira/browse/APEXCORE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reopened APEXCORE-360: -------------------------------------- > 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 > Fix For: 3.4.0 > > > 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.15#6346)