You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/09/01 17:07:05 UTC
[jira] [Updated] (BEAM-4275) Pubsub: add DirectRunner support for
id_label and timestamp_attribute in Python SDK
[ https://issues.apache.org/jira/browse/BEAM-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Beam JIRA Bot updated BEAM-4275:
--------------------------------
Priority: P3 (was: P2)
> Pubsub: add DirectRunner support for id_label and timestamp_attribute in Python SDK
> -----------------------------------------------------------------------------------
>
> Key: BEAM-4275
> URL: https://issues.apache.org/jira/browse/BEAM-4275
> Project: Beam
> Issue Type: Bug
> Components: runner-direct, sdk-py-core
> Reporter: Udi Meiri
> Priority: P3
> Labels: stale-P2
> Time Spent: 1h
> Remaining Estimate: 0h
>
> At least for publishing (and maybe pulling) messages, non-Dataflow-based sources and sinks for Pub/Sub use the [public API|https://cloud.google.com/pubsub/docs/publisher] for Pub/Sub, which doesn't support id_label and timestamp_attribute settings.
> Publishing:
> id_label - add an attribute to each message with a unique value
> timestamp_attribute - add an attribute to each message with the publishing time as its value
> Pulling:
> id_label - use the value of this message attribute to deduplicate messages
> timestamp_attribute - use the value of this message attribute as the element's timestamp
>
> Implementation details: could probably create a pubsubio.py module, for reuse with other runners (i.e. implement Pub/Sub IO as PTransforms and not NativeSinks and Sources).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)