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

Posted to issues@beam.apache.org by "Reuven Lax (Jira)" <ji...@apache.org> on 2021/07/29 20:43:00 UTC

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

Reuven Lax created BEAM-12686:
---------------------------------

             Summary: 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


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)