[
https://issues.apache.org/jira/browse/BEAM-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802158#comment-16802158
]
Jan Lukavský commented on BEAM-6873:
------------------------------------
No, the error I get is the following:
{noformat}
Class interface org.apache.beam.sdk.options.PipelineOptions missing a property
named 'project'.
at org.apache.beam.sdk.options.PipelineOptionsFactory.parseObjects
(PipelineOptionsFactory.java:1614)
at org.apache.beam.sdk.options.PipelineOptionsFactory.access$400
(PipelineOptionsFactory.java:115)
at org.apache.beam.sdk.options.PipelineOptionsFactory$Builder.as
(PipelineOptionsFactory.java:298)
at org.apache.beam.sdk.options.PipelineOptionsFactory$Builder.create
(PipelineOptionsFactory.java:278)
{noformat}
The command line is the following
{noformat}
--runner=flink --project=myProject
{noformat}
> 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)
