[
https://issues.apache.org/jira/browse/BEAM-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davor Bonaci updated BEAM-122:
------------------------------
Assignee: Mark Shields (was: Frances Perry)
> GlobalWindow and allowedLateness can cause inconsistent timer interpretation
> -----------------------------------------------------------------------------
>
> Key: BEAM-122
> URL: https://issues.apache.org/jira/browse/BEAM-122
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Mark Shields
> Assignee: Mark Shields
>
> In ReduceFnRunner we have code such as
> window.getMaxTimestamp().plus(windowingStrategy.getAllowedLateness())
> If window is global then maxTimestamp will be
> BoundedWindow.TIMESTAMP_MAX_VALUE.
> Meanwhile, timestamps beyond BoundedWindow.TIMESTAMP_MAX_VALUE will be
> clipped in most runners.
> This could cause the time of an expected timer (eg for garbage collection) to
> not match the actual time of a fired timer.
> We should either make non-zero allowedLateness on the Global window illegal
> (probably obnoxious) or explicitly clip it to zero.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
