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 8BAB5200B7C for ; Thu, 8 Sep 2016 21:48:59 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8A2DC160ABD; Thu, 8 Sep 2016 19:48:59 +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 CFC66160AAD for ; Thu, 8 Sep 2016 21:48:58 +0200 (CEST) Received: (qmail 80643 invoked by uid 500); 8 Sep 2016 19:48:57 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 80631 invoked by uid 99); 8 Sep 2016 19:48:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Sep 2016 19:48:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 475171A5E07 for ; Thu, 8 Sep 2016 19:48:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id v_mTrCvJj-F6 for ; Thu, 8 Sep 2016 19:48:55 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 4A2EC5F1B3 for ; Thu, 8 Sep 2016 19:48:55 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id 337964ACBE75B for ; Thu, 8 Sep 2016 12:48:53 -0700 (MST) Date: Thu, 8 Sep 2016 12:45:39 -0700 (PDT) From: "aj.h" To: user@flink.apache.org Message-ID: <1473363939426-8975.post@n4.nabble.com> In-Reply-To: References: Subject: Re: Firing windows multiple times MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 08 Sep 2016 19:48:59 -0000 Hi, I'm interested in helping out on this project. I also want to implement a continuous time-boxed sliding window, my current use case is a 60-second sliding window that moves whenever a newer event arrives, discarding any late events that arrive outside the current window, but *also* re-triggering window processing for any late events within the current window. I considered using sliding windows with a 1-second granularity, but I'd be discarding a lot of windows on sparse data, and rebuilding pontetially very large windows for relatively small 1-second updates. I'm a fellow in the Insight Data Engineering program. We just got underway, and I have 3 weeks in which to complete a project. I'd love to tackle this one, and I'm trying to assess the practicality and feasibility of it. I noticed that FLIP-2 and FLIP-4 are still under discussion; is it premature to try to implement these enhancements? And would you be at all willing/available to help me get up to speed? Thank you much! -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Firing-windows-multiple-times-tp8424p8975.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.