[ 
https://issues.apache.org/jira/browse/BEAM-12931?focusedWorklogId=658638&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-658638
 ]

ASF GitHub Bot logged work on BEAM-12931:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Sep/21 22:32
            Start Date: 30/Sep/21 22:32
    Worklog Time Spent: 10m 
      Work Description: laraschmidt commented on a change in pull request 
#15540:
URL: https://github.com/apache/beam/pull/15540#discussion_r719810671



##########
File path: 
runners/core-java/src/main/java/org/apache/beam/runners/core/SimpleDoFnRunner.java
##########
@@ -1190,13 +1190,20 @@ public Timer withOutputTimestamp(Instant 
outputTimestamp) {
      * </ul>
      */
     private void setAndVerifyOutputTimestamp() {
-
       if (outputTimestamp != null) {
-        checkArgument(
-            !outputTimestamp.isBefore(elementInputTimestamp),
-            "output timestamp %s should be after input message timestamp or 
output timestamp of firing timers %s",
-            outputTimestamp,
-            elementInputTimestamp);
+        // The documentation of getAllowedTimestampSkew explicitly permits 
Long.MAX_VALUE to be used
+        // for infinite skew. Defend against underflow in that case for 
timestamps before the epoch.
+        if (fn.getAllowedTimestampSkew().getMillis() != Long.MAX_VALUE

Review comment:
       Sounds good.

##########
File path: 
runners/core-java/src/main/java/org/apache/beam/runners/core/SimpleDoFnRunner.java
##########
@@ -1190,13 +1190,20 @@ public Timer withOutputTimestamp(Instant 
outputTimestamp) {
      * </ul>
      */
     private void setAndVerifyOutputTimestamp() {
-
       if (outputTimestamp != null) {
-        checkArgument(
-            !outputTimestamp.isBefore(elementInputTimestamp),
-            "output timestamp %s should be after input message timestamp or 
output timestamp of firing timers %s",
-            outputTimestamp,
-            elementInputTimestamp);
+        // The documentation of getAllowedTimestampSkew explicitly permits 
Long.MAX_VALUE to be used
+        // for infinite skew. Defend against underflow in that case for 
timestamps before the epoch.
+        if (fn.getAllowedTimestampSkew().getMillis() != Long.MAX_VALUE

Review comment:
       Sounds good. Done.




-- 
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: 658638)
    Time Spent: 1h 10m  (was: 1h)

> Timer.setOutputTimestamp doesn't take into account for 
> DoFn#getAllowedTimestampSkew()
> -------------------------------------------------------------------------------------
>
>                 Key: BEAM-12931
>                 URL: https://issues.apache.org/jira/browse/BEAM-12931
>             Project: Beam
>          Issue Type: Bug
>          Components: beam-model
>            Reporter: Lara Schmidt
>            Assignee: Lara Schmidt
>            Priority: P2
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> A DoFn may emit elements with a timestamp up to 
> DoFn#getAllowedTimestampSkew() before the current element's timestamp. 
> However getAllowedTimestampSkew is not properly accounted for in looking at 
> the output timestamp of a timer.
> Context: 
> [https://lists.apache.org/thread.html/r7554658114ddde86c5d82e1c39fe7e1ef587fe926b8e406d1130d501%40%3Cdev.beam.apache.org%3E]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to