[
https://issues.apache.org/jira/browse/BEAM-14244?focusedWorklogId=753433&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-753433
]
ASF GitHub Bot logged work on BEAM-14244:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/22 14:24
Start Date: 06/Apr/22 14:24
Worklog Time Spent: 10m
Work Description: je-ik commented on PR #17262:
URL: https://github.com/apache/beam/pull/17262#issuecomment-1090333843
> testTeardownCalledAfterExceptionInStartBundleStateful again
This one is unrelated to timers. The one that I saw the first time looked
like it could be related.
Issue Time Tracking
-------------------
Worklog Id: (was: 753433)
Time Spent: 6.5h (was: 6h 20m)
> Processing time timers should use outputTimestamp rather than input watermark
> for their timestamp
> -------------------------------------------------------------------------------------------------
>
> Key: BEAM-14244
> URL: https://issues.apache.org/jira/browse/BEAM-14244
> Project: Beam
> Issue Type: Bug
> Components: runner-core, sdk-java-core
> Reporter: Steve Niemitz
> Assignee: Steve Niemitz
> Priority: P1
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> Currently processing time timers ignore the outputTimestamp and instead use
> the input watermark at the time they fire. This is wrong because the input
> watermark can have advanced arbitrarily far past the actual output timestamp
> when it fires.
> The correct behavior should be to instead use the outputTimestamp the timer
> was configured to fire with.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
