[
https://issues.apache.org/jira/browse/BEAM-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132000#comment-17132000
]
Beam JIRA Bot commented on BEAM-1936:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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.3.4#803005)
