You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Robert Bradshaw (Jira)" <ji...@apache.org> on 2020/05/28 23:31:00 UTC
[jira] [Resolved] (BEAM-8532) Beam Python trigger driver sets
incorrect timestamp for output windows.
[ https://issues.apache.org/jira/browse/BEAM-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Bradshaw resolved BEAM-8532.
-----------------------------------
Fix Version/s: 2.20.0
Resolution: Fixed
> Beam Python trigger driver sets incorrect timestamp for output windows.
> -----------------------------------------------------------------------
>
> Key: BEAM-8532
> URL: https://issues.apache.org/jira/browse/BEAM-8532
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Robert Bradshaw
> Assignee: Robert Bradshaw
> Priority: P1
> Fix For: 2.20.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The timestamp should lie in the window, otherwise re-windowing will not be idempotent.
> https://github.com/apache/beam/blob/release-2.16.0/sdks/python/apache_beam/transforms/trigger.py#L1183 should be using {{window.max_timestamp()}} rather than {{.end}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)