[
https://issues.apache.org/jira/browse/BEAM-9804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141637#comment-17141637
]
Tyler Krusenstjerna commented on BEAM-9804:
-------------------------------------------
Still requesting feature parity for python, java has this functionality per
BEAM-8458 https://issues.apache.org/jira/browse/BEAM-8458
> beam.io.BigQuerySource needs permissions to create datasets to be able to run
> queries
> -------------------------------------------------------------------------------------
>
> Key: BEAM-9804
> URL: https://issues.apache.org/jira/browse/BEAM-9804
> Project: Beam
> Issue Type: Bug
> Components: io-py-gcp
> Reporter: Jonathan Sulman
> Priority: P2
> Labels: stale-P2
>
> Based on BEAM-8458, which was closed with a Java fix in 2.20.0. However, the
> bug still exists in the python SDK.
> When using BigQuerySource with the query option, BigQueryReader creates a
> temporary dataset to store the results of the query.
> Therefore, Beam requires permissions to create datasets just to be able to
> run a query. In practice, this means that Beam requires the role
> bigQuery.User just to run queries, whereas if you use {{from}} (to read from
> a table), the role bigQuery.jobUser suffices.
> BigqueryDataSource should have an option to set an existing dataset to write
> the temp results of
> a query, so it would be enough with having the role bigQuery.jobUser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
