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 2020/05/15 22:55:00 UTC

[jira] [Work logged] (BEAM-10015) output timestamp not properly propagated through the Dataflow runner

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

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

                Author: ASF GitHub Bot
            Created on: 15/May/20 22:54
            Start Date: 15/May/20 22:54
    Worklog Time Spent: 10m 
      Work Description: reuvenlax commented on pull request #11725:
URL: https://github.com/apache/beam/pull/11725#issuecomment-629539400


   R: @rehmanmuradali 


----------------------------------------------------------------
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: 433963)
    Remaining Estimate: 0h
            Time Spent: 10m

> output timestamp not properly propagated through the Dataflow runner
> --------------------------------------------------------------------
>
>                 Key: BEAM-10015
>                 URL: https://issues.apache.org/jira/browse/BEAM-10015
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Reuven Lax
>            Priority: Critical
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Dataflow runner does not propagate the output timestamp into timer firing, resulting in incorrect default timestamps when outputting from a processTimer.



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