[jira] [Commented] (BEAM-11632) Guardrails around fromTopic (pubsub)

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-11632:
--------------------------------------

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.


> Guardrails around fromTopic (pubsub)
> ------------------------------------
>
>                 Key: BEAM-11632
>                 URL: https://issues.apache.org/jira/browse/BEAM-11632
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-gcp, io-py-gcp
>            Reporter: Ahmet Altay
>            Priority: P2
>              Labels: stale-P2
>
> Fundamentally, we should strongly discourage the use of ephemeral topics (fromTopic() in PubsubIO) in favor of user-created subscriptions. Currently, the documentation for fromTopic states this matter-of-factly, without drawing attention to the fact that this is almost certainly *not* what the wants:
> {quote}The Beam runner will start reading data published on this topic from the time the pipeline is started. Any data published on the topic before the pipeline is started will not be read by the runner.{quote}
> Suggestion: We should include an execution warning whenever fromTopic is used, as well as update the documentation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)