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

Posted to issues@beam.apache.org by "Mikhail Gryzykhin (JIRA)" <ji...@apache.org> on 2019/06/26 22:45:00 UTC

[jira] [Updated] (BEAM-7642) (Dataflow) Python AfterProcessingTime fires before defined time

     [ https://issues.apache.org/jira/browse/BEAM-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Gryzykhin updated BEAM-7642:
------------------------------------
    Summary: (Dataflow) Python AfterProcessingTime fires before defined time  (was: (Dataflow) AfterProcessingTime fires before defined time)

> (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)