You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Lara Schmidt (Jira)" <ji...@apache.org> on 2022/01/12 17:37:00 UTC

[jira] [Commented] (BEAM-12931) Timer.setOutputTimestamp doesn't take into account for DoFn#getAllowedTimestampSkew()

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

Lara Schmidt commented on BEAM-12931:
-------------------------------------

There's still one check remaining that needs to be added in the portable runner case but could not be because of a unfixed bug in the dataflow side. It's only a one line change though and there's a TODO so I can close this.

> 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: 8h 50m
>  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.20.1#820001)