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/06/28 19:57:00 UTC

[jira] [Resolved] (BEAM-1696) Allow explicit output time for processing time timers

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

Kenneth Knowles resolved BEAM-1696.
-----------------------------------
       Resolution: Duplicate
         Assignee: Kenneth Knowles
    Fix Version/s: Not applicable

> Allow explicit output time for processing time timers
> -----------------------------------------------------
>
>                 Key: BEAM-1696
>                 URL: https://issues.apache.org/jira/browse/BEAM-1696
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>             Fix For: Not applicable
>
>
> Today, a processing time timer is not associated with a particular output timestamp; instead the user must explicitly output to the desired timestamp.
> This has a few drawbacks:
>  - Probably need to maintain state that indicates what the timestamp should be
>  - The output watermark is not held to that timestamp
> Something like {{processingTimer.set(...).withOutputTimestamp(...)}} (or perhaps some more involved API with an {{OutputTimeFn}}-like policy attached) would work nicely, so when {{@OnTimer}} is called the right timestamp is automatic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)