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

["Ismaël Mejía (Jira)" <ji...@apache.org>]

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

Ismaël Mejía edited comment on BEAM-10015 at 5/30/20, 3:45 PM:
---------------------------------------------------------------

Spark Runner Timers tests are broken since this was merged. Worth to fix before the RC
https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark/7440/testReport/


was (Author: iemejia):
Spark Runner Timers tests are broken since this was merged
https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark/7440/testReport/

> 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
>            Assignee: Reuven Lax
>            Priority: P1
>             Fix For: 2.22.0
>
>          Time Spent: 40m
>  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)