[
https://issues.apache.org/jira/browse/BEAM-14244?focusedWorklogId=753481&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-753481
]
ASF GitHub Bot logged work on BEAM-14244:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/22 15:58
Start Date: 06/Apr/22 15:58
Worklog Time Spent: 10m
Work Description: reuvenlax commented on code in PR #17262:
URL: https://github.com/apache/beam/pull/17262#discussion_r844120506
##########
runners/core-java/src/main/java/org/apache/beam/runners/core/SimpleDoFnRunner.java:
##########
@@ -209,7 +209,12 @@ public void processElement(WindowedValue<InputT>
compressedElem) {
break;
case PROCESSING_TIME:
case SYNCHRONIZED_PROCESSING_TIME:
- effectiveTimestamp =
stepContext.timerInternals().currentInputWatermarkTime();
+ Instant outputWatermark =
stepContext.timerInternals().currentOutputWatermarkTime();
+ Instant inputWatermark =
stepContext.timerInternals().currentInputWatermarkTime();
+ effectiveTimestamp =
+ outputTimestamp != null
+ ? outputTimestamp
+ : outputWatermark != null ? outputWatermark : inputWatermark;
Review Comment:
I'm still not sure why outputTimestamp would ever be null! Does flink set it
to null?
Issue Time Tracking
-------------------
Worklog Id: (was: 753481)
Time Spent: 7h (was: 6h 50m)
> 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: 7h
> 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)
