[
https://issues.apache.org/jira/browse/BEAM-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006494#comment-16006494
]
Borisa Zivkovic commented on BEAM-400:
--------------------------------------
I think correct behavior is implemented in current Pubsub client
implementations (grpc and json). It would be good if someone with more
experience can confirm this.
> 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)
