flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4239) Set Default Allowed Lateness to Zero and Make Triggers Non-Purging
Date Mon, 25 Jul 2016 14:32:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391997#comment-15391997
] 

ASF GitHub Bot commented on FLINK-4239:
---------------------------------------

Github user kl0u commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2278#discussion_r72073857
  
    --- Diff: flink-streaming-java/src/test/java/org/apache/flink/streaming/runtime/operators/windowing/WindowOperatorTest.java
---
    @@ -1409,7 +1409,7 @@ public void testDropDueToLatenessSliding() throws Exception {
     	}
     
     	@Test
    -	public void testDropDueToLatenessSessionZeroLateness() throws Exception {
    +	public void testDropDueToLatenessSessionZeroLatenessPurgingTrigger() throws Exception
{
     		final int GAP_SIZE = 3;
     		final long LATENESS = 0;
     
    --- End diff --
    
    Here the name changes to indicate that it is purging, but the Trigger is the same (EventTime)
without purging.


> Set Default Allowed Lateness to Zero and Make Triggers Non-Purging
> ------------------------------------------------------------------
>
>                 Key: FLINK-4239
>                 URL: https://issues.apache.org/jira/browse/FLINK-4239
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Streaming
>    Affects Versions: 1.1.0
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>
> In preparation for upcoming changes in 1.2 we should set the default allowed lateness
to zero and make all built-in triggers non-purging by default. 
> Currently, {{EventTimeTrigger}} and {{ProcessingTimeTrigger}} purge when they fire. This
leads to unexpected behavior when a user sets some meaningful allowed lateness. The behavior
will be that the window is purged when firing and the state will not actually be kept within
the allowed lateness.
> Changing the behavior to non-purging requires changing the default allowed lateness from
{{Long.MAX_VALUE}} to {{0}}. Otherwise we would have memory leaks.



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

Mime
View raw message