[
https://issues.apache.org/jira/browse/BEAM-12276?focusedWorklogId=592894&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-592894
]
ASF GitHub Bot logged work on BEAM-12276:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/May/21 17:50
Start Date: 04/May/21 17:50
Worklog Time Spent: 10m
Work Description: je-ik commented on pull request #14718:
URL: https://github.com/apache/beam/pull/14718#issuecomment-832128322
No, you can verify that by running the test without the changed precondition.
I'm not sure if relative timer based ob element's timestamp makes sense to
me. Using input watermark makes perfect analogy with relative processing time
timers, at least as I understand the concept.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 592894)
Time Spent: 2h 10m (was: 2h)
> Timer.withOutputTimestamp(Instant).offset(Duration).setRelative() might fail
> unexpectedly
> -----------------------------------------------------------------------------------------
>
> Key: BEAM-12276
> URL: https://issues.apache.org/jira/browse/BEAM-12276
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Affects Versions: 2.30.0
> Reporter: Jan Lukavský
> Assignee: Jan Lukavský
> Priority: P2
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> We check that timer's output timestamp is not before timer fire timestamp.
> The fire timestamp is unknown to user when setting a relative timer and
> therefore cannot be checked in user code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
