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

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 1.1
• Assignee: Bharath Kumarasubramanian
• Reporter: Prateek Maheshwari
• Created: 07/Nov/18 19:33
• Updated: 22/Jul/19 20:38

Description

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.