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

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/10/12 17:25:01 UTC

[jira] [Updated] (BEAM-12686) Support self-managed relative timers

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

Beam JIRA Bot updated BEAM-12686:
---------------------------------
    Priority: P3  (was: P2)

> Support self-managed relative timers
> ------------------------------------
>
>                 Key: BEAM-12686
>                 URL: https://issues.apache.org/jira/browse/BEAM-12686
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Reuven Lax
>            Priority: P3
>              Labels: stale-P2
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Relative timers can be set today using Timer.offset().setRelative(). However there are use cases in which a DoFn needs to maintain the timer timestamp in state and use this as the relative offset (e.g. so it can later update just the output timestamp without modifying the fire timestamp). This is impossible today for several reasons
>    - Processing-time timers disallow set(), only setRelative() is allowed.
>    - There's no way of knowing what the base value for setRelative is. Using the system-provided base value is important as otherwise tests using TestStream will not work correctly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)