You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Prateek Maheshwari (JIRA)" <ji...@apache.org> on 2018/11/07 19:34:00 UTC

[jira] [Updated] (SAMZA-1982) Use TimerRegistry to track time based window triggers instead of relying on window()

     [ https://issues.apache.org/jira/browse/SAMZA-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prateek Maheshwari updated SAMZA-1982:
--------------------------------------
    Fix Version/s: 1.1

> Use TimerRegistry to track time based window triggers instead of relying on window()
> ------------------------------------------------------------------------------------
>
>                 Key: SAMZA-1982
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1982
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Prateek Maheshwari
>            Assignee: Prateek Maheshwari
>            Priority: Major
>             Fix For: 1.1
>
>
> Now that we have support for arbitrary processing time timer callbacks (TimerRegistry), we can switch from window() call based triggers to using more precise triggers. Currently we set the window interval to be the GCD of all window intervals. This has the disadvantage of keeping session windows open longer than necessary, since in the worst case a new message has up to 2 * window time to arrive.



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