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

Posted to commits@beam.apache.org by "Borisa Zivkovic (JIRA)" <ji...@apache.org> on 2017/05/04 10:54:04 UTC

[jira] [Commented] (BEAM-400) Direct/InProcess runner should use Pubsub publish time timestamp if timestampLabel is not set

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

Borisa Zivkovic commented on BEAM-400:
--------------------------------------

I can take this if this is still valid?

> Direct/InProcess runner should use Pubsub publish time timestamp if timestampLabel is not set
> ---------------------------------------------------------------------------------------------
>
>                 Key: BEAM-400
>                 URL: https://issues.apache.org/jira/browse/BEAM-400
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-gcp
>            Reporter: Daniel Mills
>            Priority: Minor
>              Labels: newbie, starter
>
> When using system-provided timestamps for PubsubIO, the timestamp should be the time at which the message was published to Pubsub, not when it was received by the pipeline.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)