[
https://issues.apache.org/jira/browse/BEAM-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-1936:
----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the
pull request resolve the issue? If so, could you please mark it resolved? This
will help the project have a clear view of its open issues.
> Allow user provided function to extract custom timestamp from payload in
> pubsubIO
> ---------------------------------------------------------------------------------
>
> Key: BEAM-1936
> URL: https://issues.apache.org/jira/browse/BEAM-1936
> Project: Beam
> Issue Type: New Feature
> Components: io-java-gcp
> Reporter: Keith Berkoben
> Priority: P3
>
> Currently the PubsubIO runner only allows the caller to set a custom
> timestamp if the timestamp is defined in the attributes of the message. This
> can be problematic when the user does not control the publisher. In such a
> case, proper windowing of data requires the timestamp to be pulled out of the
> message payload.
> Since a payload could have arbitrary data, the user would have to provide a
> Function<T, String>() that would extract the timestamp from the payload:
> PubsubIo.Read.timestampLabel(Function<T, String> extractor);
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
