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 F127A200B9D for ; Thu, 13 Oct 2016 16:23:39 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EF9FF160AE4; Thu, 13 Oct 2016 14:23:39 +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 429A9160AE3 for ; Thu, 13 Oct 2016 16:23:39 +0200 (CEST) Received: (qmail 3813 invoked by uid 500); 13 Oct 2016 14:23:38 -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 3803 invoked by uid 99); 13 Oct 2016 14:23:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Oct 2016 14:23:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E6106C18E0 for ; Thu, 13 Oct 2016 14:23:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.313 X-Spam-Level: * X-Spam-Status: No, score=1.313 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id SO-tdY8iyodv for ; Thu, 13 Oct 2016 14:23:36 +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 2E3F35F647 for ; Thu, 13 Oct 2016 14:23:36 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id B767F59711975 for ; Thu, 13 Oct 2016 07:23:35 -0700 (MST) Date: Thu, 13 Oct 2016 07:16:22 -0700 (PDT) From: swiesman To: user@flink.apache.org Message-ID: <1476368182836-9529.post@n4.nabble.com> Subject: Allowed Lateness and Window State MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 13 Oct 2016 14:23:40 -0000 Hi all, I have a question about allowed lateness semantics and window state. I have a custom event time trigger that does an early FIRE onElement for a certain set of conditions and then a FIRE_AND_PURGE onEventTime. And this has worked great for me. However I now want to add a certain amount of allowed lateness to this window. My understanding has been that when TriggerResult.FIRE_AND_PURGE is returned the window will be fully evaluated and the state cleared. So if a new element shows up in the allowed lateness time will it be put into a new singleton window and evaluated or does specifying allowed lateness defer the window purge until after the allowed lateness has passed? Put another way, in the illustration below if my window is counting circles after the red circle is seen will my window output 5 or 1? If I want it to output 5 do I have to modify my trigger? Thank you, Seth Wiesman -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Allowed-Lateness-and-Window-State-tp9529.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.