[
https://issues.apache.org/jira/browse/BEAM-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873721#comment-16873721
]
Daniel Mills commented on BEAM-7642:
------------------------------------
Looks like the issue is a seconds/milliseconds mixup when translating to runner
API protos from the AfterProcessingTime trigger:
[https://github.com/apache/beam/blob/master/sdks/python/apache_beam/transforms/trigger.py#L336]
sets the delay_millis field of the proto to self.delay, which is in seconds:
[https://github.com/apache/beam/blob/master/sdks/python/apache_beam/transforms/trigger.py#L299]
Also need to fix the reverse direction:
[https://github.com/apache/beam/blob/master/sdks/python/apache_beam/transforms/trigger.py#L330]
> (Dataflow) Python AfterProcessingTime fires before defined time
> ---------------------------------------------------------------
>
> Key: BEAM-7642
> URL: https://issues.apache.org/jira/browse/BEAM-7642
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Mikhail Gryzykhin
> Priority: Major
>
> [https://stackoverflow.com/questions/56700913/why-my-data-in-apache-beam-is-emitted-after-a-few-minutes-instead-of-10h]
>
> User on StackOverflow has a problem that AfterProcessingTime on global window
> fires before allocated time (10h). It dumps events within first
> minutes/seconds and then drops the rest due to window closed.
> Code user provided seems valid. I tried to verify time units accepted by the
> method, but I couldn't track it all the way through the code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
