[
https://issues.apache.org/jira/browse/BEAM-8458?focusedWorklogId=332167&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-332167
]
ASF GitHub Bot logged work on BEAM-8458:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Oct/19 19:35
Start Date: 22/Oct/19 19:35
Worklog Time Spent: 10m
Work Description: iht commented on issue #9852: [BEAM-8458] Add option to
set temp dataset in BigQueryIO.Read
URL: https://github.com/apache/beam/pull/9852#issuecomment-545119172
R: @chamikaramj
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 332167)
Time Spent: 20m (was: 10m)
> 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
> 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)
