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-8384) Session Window Assigner with Dynamic Gaps
Date Wed, 31 Jan 2018 15:34:00 GMT

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

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

Github user dyanarose commented on the issue:

    https://github.com/apache/flink/pull/5295
  
    Ah, I hadn't thought to keep both in place. So unless the Dynamic SessionWindow classes
had withDynamicGap made package private, you would then be able to instantiate them from two
different classes. That could feel a bit iffy, however someone else would call it a convenience
method. 
    
    I'll get the change in for the Trigger cast, that should clean up the PR a fair bit


> Session Window Assigner with Dynamic Gaps
> -----------------------------------------
>
>                 Key: FLINK-8384
>                 URL: https://issues.apache.org/jira/browse/FLINK-8384
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming
>            Reporter: Dyana Rose
>            Priority: Minor
>
> *Reason for Improvement*
> Currently both Session Window assigners only allow a static inactivity gap. 
> Given the following scenario, this is too restrictive:
> * Given a stream of IoT events from many device types
> * Assume each device type could have a different inactivity gap
> * Assume each device type gap could change while sessions are in flight
> By allowing dynamic inactivity gaps, the correct gap can be determined in the [assignWindows
function|https://github.com/apache/flink/blob/master/flink-streaming-java/src/main/java/org/apache/flink/streaming/api/windowing/assigners/EventTimeSessionWindows.java#L59]
by passing the element currently under consideration, the timestamp, and the context to a
user defined function. This eliminates the need to create unwieldy work arounds if you only
have static gaps.
> Dynamic Session Window gaps should be available for both Event Time and Processing Time
streams.
> (short preliminary discussion: https://lists.apache.org/thread.html/08a011c0039e826343e9be0b1bb4e0000cfc2e12976bc65f8a43ee88@%3Cdev.flink.apache.org%3E)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message