[
https://issues.apache.org/jira/browse/BEAM-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798339#comment-16798339
]
Jan Lukavský commented on BEAM-6873:
------------------------------------
Sure, that's why it should be possible to override this by {{GcpOptions}}. But
if you run with runner that is not bound to GCP (e.g. flink), then there is
currently no (simple) way to specify the project and it is not taken from the
topic, which is somehow suboptimal.
> Simplify PubsubIO projectId management
> --------------------------------------
>
> Key: BEAM-6873
> URL: https://issues.apache.org/jira/browse/BEAM-6873
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Affects Versions: 2.11.0
> Reporter: Jan Lukavský
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> PubsubIO uses some (probably) legacy code around projectId management, which
> among several other suboptimalities causes pipelines without
> {{GcpOptions.project}} specified to fail. This is not necessary, because
> projectId is already contained in {{projects/<project>/topics/<topic>}} when
> reading specified topic. The projectId should be read from there and
> (possibly to maintain backwards compatibility) be overridden by GcpOptions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
