CODEWITHSUNDEEP
google-bigquery
pompanoSlayer
pompanoSlayer

Reputation: 163

Bigquery: A "READER" but not writer. Can he/she query the table in that dataset within the project that contain the data?

I have read this over and over again. https://cloud.google.com/bigquery/access-control

The question is: If I were to give a user "READER" access to a dataset only. No dataset "Writer" or project "Can Edit" that contains the dataset. This user query the table in the dataset from his/her project and doesn't save it into a table (basically bigquery create a temp table). I guess a better question is, is this temp table being saved in the user project or in the same project as where the data originated.

My assumption is in the project he runs, as the billing account for his/her project is going to get billed for it. Is this a correct assumption?

Upvotes: 2

Views: 204

Answers (2)

Jeremy Condit
Jeremy Condit

Reputation: 7046

The temp table created by a query job is created in the project in which the query job ran.

The temp table will be created as a side-effect of the query even if the user only has "Can View" access to the project, since that's all that's required to run a query.

The only charges incurred are the charges for the query itself, since there are no storage costs incurred for temp tables created by a query.

Upvotes: 0

DoiT International
DoiT International

Reputation: 2435

Yes, this is correct assumption. If the user has a READER permission in the dataset and doesn't have access to the project itself, this user won't be able to run queries unless he is part of some project with enabled billing.

Upvotes: 1

Related Questions