[
https://issues.apache.org/jira/browse/BEAM-9728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131620#comment-17131620
]
Beam JIRA Bot commented on BEAM-9728:
-------------------------------------
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.
> PubsubIO.Read support for timestamp parsing
> -------------------------------------------
>
> Key: BEAM-9728
> URL: https://issues.apache.org/jira/browse/BEAM-9728
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Oleksandr Bushkovskyi
> Priority: P2
> Labels: stale-P2
>
> Hi,
> I'm repeatedly facing situations where I need to assign timestamp from PubSub
> message body and it's not possible via Pubsub.Read.
> Having some method like
> `withTimestampFn(SerializableFunction<ReceivedMessage, Long>)` would be very
> helpfull.
> BEAM-53 mention such feature:
> ??getting timestamp from an arbitrary lambda in arbitrary formats rather than
> from a message attribute in only 2 formats.??
> But looks that it was never implemented.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
