[
https://issues.apache.org/jira/browse/BEAM-12686?focusedWorklogId=631931&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-631931
]
ASF GitHub Bot logged work on BEAM-12686:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 31/Jul/21 02:53
Start Date: 31/Jul/21 02:53
Worklog Time Spent: 10m
Work Description: reuvenlax commented on pull request #15247:
URL: https://github.com/apache/beam/pull/15247#issuecomment-890280985
Run Java Flink PortableValidatesRunner Streaming
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 631931)
Time Spent: 1h (was: 50m)
> 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
> Time Spent: 1h
> 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)
