[
https://issues.apache.org/jira/browse/BEAM-11632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295432#comment-17295432
]
Beam JIRA Bot commented on BEAM-11632:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Guardrails around fromTopic (pubsub)
> ------------------------------------
>
> Key: BEAM-11632
> URL: https://issues.apache.org/jira/browse/BEAM-11632
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp, io-py-gcp
> Reporter: Ahmet Altay
> Assignee: Chamikara Madhusanka Jayalath
> Priority: P2
> Labels: stale-assigned
>
> 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)
