[
https://issues.apache.org/jira/browse/BEAM-12276?focusedWorklogId=595108&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-595108
]
ASF GitHub Bot logged work on BEAM-12276:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/May/21 07:47
Start Date: 12/May/21 07:47
Worklog Time Spent: 10m
Work Description: je-ik commented on a change in pull request #14718:
URL: https://github.com/apache/beam/pull/14718#discussion_r630804066
##########
File path:
runners/core-java/src/main/java/org/apache/beam/runners/core/SimpleDoFnRunner.java
##########
@@ -1219,11 +1219,11 @@ private void setAndVerifyOutputTimestamp() {
Instant windowExpiry = window.maxTimestamp().plus(allowedLateness);
if (TimeDomain.EVENT_TIME.equals(spec.getTimeDomain())) {
checkArgument(
- !outputTimestamp.isAfter(target),
+ !outputTimestamp.isAfter(windowExpiry),
Review comment:
Forcing the output timestamp to be before the end of the window is
actually quite logical requirement, but is a breaking change. It will break
code that sets timer (without output timestamp) to endOfWindow + lateness.
Therefore I think we must keep the check as it is. Yes, it might result in data
from a particular window being emitted for a different window (which really
seems like a bug).
--
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: 595108)
Time Spent: 3h 10m (was: 3h)
> 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: 3h 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)
