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

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2017/04/20 04:00:06 UTC

[jira] [Commented] (BEAM-2022) ApexTimerInternals seems to treat processing time timers as event time timers

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

Kenneth Knowles commented on BEAM-2022:
---------------------------------------

If this is the case, and is not fixable quickly, we can add static validation of a graph to reject such timers.

> ApexTimerInternals seems to treat processing time timers as event time timers
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-2022
>                 URL: https://issues.apache.org/jira/browse/BEAM-2022
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-apex
>            Reporter: Kenneth Knowles
>            Assignee: Thomas Weise
>             Fix For: First stable release
>
>
> I first noticed that {{currentProcessingTime()}} was using {{Instant.now()}}, which has some bad issues in a distributed setting. But it seemed on inspection that processing time timers are simply treated as event time. Perhaps I am reading the code wrong?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)