You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "tamir (Jira)" <ji...@apache.org> on 2022/01/21 14:00:00 UTC

[jira] [Commented] (BEAM-13532) Pubsub-IO dynamic destination

    [ https://issues.apache.org/jira/browse/BEAM-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480087#comment-17480087 ] 

tamir commented on BEAM-13532:
------------------------------

[~kenn] the pull-request resolve the issue for pubsub-io implementation. but in order to run on DataFlow it requires changes in the runner because it has internal implementation for sending the request to pubsub.
It is open for discussion in the devs-list https://lists.apache.org/thread/s64yx0w3yqp5l481181sz5h2z6x3r57j 

> Pubsub-IO dynamic destination
> -----------------------------
>
>                 Key: BEAM-13532
>                 URL: https://issues.apache.org/jira/browse/BEAM-13532
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-java-gcp
>            Reporter: tamir
>            Assignee: tamir
>            Priority: P2
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Change topic name to be part of the PubsubMessage and pass it using dynamic destinations (like in BigQuery-IO). This will allow writing to new topics without restart the job.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)