beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1696) Allow explicit output time for processing time timers
Date Mon, 13 Mar 2017 04:07:04 GMT

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

Kenneth Knowles commented on BEAM-1696:
---------------------------------------

That is a fair point. I don't have a confident understanding of whether BEAM-1697 should just
be rolled into this or not. Probably yes.

> 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
>
> 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.3.15#6346)

Mime
View raw message