[
https://issues.apache.org/jira/browse/BEAM-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421539#comment-17421539
]
Beam JIRA Bot commented on BEAM-12686:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> 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)
