[
https://issues.apache.org/jira/browse/BEAM-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Herraiz updated BEAM-8458:
---------------------------------
Description:
When using {{fromQuery}}, BigQueryIO creates a temp 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.
BigQueryIO.Read 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.
was:
When using `fromQuery`, BigQueryIO creates a temp 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.
BigQueryIO.Read 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.
> BigQueryIO.Read needs permissions to create datasets to run queries
> -------------------------------------------------------------------
>
> Key: BEAM-8458
> URL: https://issues.apache.org/jira/browse/BEAM-8458
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Reporter: Israel Herraiz
> Assignee: Israel Herraiz
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When using {{fromQuery}}, BigQueryIO creates a temp 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.
> BigQueryIO.Read 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)
