You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/03/02 00:22:00 UTC

[jira] [Work logged] (BEAM-11868) Python AfterProcessingTime triggers result in additional delay at each GBK

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

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

                Author: ASF GitHub Bot
            Created on: 02/Mar/21 00:21
            Start Date: 02/Mar/21 00:21
    Worklog Time Spent: 10m 
      Work Description: kennknowles commented on pull request #14060:
URL: https://github.com/apache/beam/pull/14060#issuecomment-788425698


   Friendly ping. LMK if I'm going about this wrong. New to the codebase and being very simple about things.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 559666)
    Time Spent: 20m  (was: 10m)

> Python AfterProcessingTime triggers result in additional delay at each GBK
> --------------------------------------------------------------------------
>
>                 Key: BEAM-11868
>                 URL: https://issues.apache.org/jira/browse/BEAM-11868
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: P2
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> See thread discussing it: https://lists.apache.org/thread.html/rd1b59fead3927b8769514f65fa66c051f80f68a6115dae356e86302c%40%3Cdev.beam.apache.org%3E
> The solution is to switch to match Java and have "AfterSynchronizedProcessingTime" but also to allow a runner to ignore that trigger and do whatever it wants.



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