Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine what values can come back as BQ access roles #1050

Closed
dhermes opened this issue Aug 11, 2015 · 7 comments
Closed

Determine what values can come back as BQ access roles #1050

dhermes opened this issue Aug 11, 2015 · 7 comments
Assignees
Labels
api: bigquery Issues related to the BigQuery API.

Comments

@dhermes
Copy link
Contributor

dhermes commented Aug 11, 2015

See #1046

@dhermes dhermes added the api: bigquery Issues related to the BigQuery API. label Aug 11, 2015
@dhermes
Copy link
Contributor Author

dhermes commented Aug 11, 2015

From the original PR:

@fhoffa Is it possible for there to be more than one key in an "access" (ACL) object returned?

The spec indicates

    {
      "role": "...",
      "userByEmail": "...",
      "groupByEmail": "...",
      "domain": "...",
      "specialGroup": "...",
      "view": {
        "projectId": "...",
        "datasetId": "...",
        "tableId": "..."
      }
    }

but empirically @tseaver seems to only be seeing one key and it is always one of userByEmail, groupByEmail and specialGroup.

@dhermes
Copy link
Contributor Author

dhermes commented Dec 31, 2015

@jgeewax Is there someone who works on BigQuery we can reach out to?

@fhoffa
Copy link

fhoffa commented Dec 31, 2015

bumping internally!

@dhermes
Copy link
Contributor Author

dhermes commented Dec 31, 2015

Thanks @fhoffa!

@jcondit
Copy link

jcondit commented Dec 31, 2015

BQ engineer here. Every entry in the access list will have exactly one of userByEmail, groupByEmail, domain, specialGroup, or view set. And if anything but view is set, it'll also have a role specified (role is omitted for a view, since views are always read-only, though arguably we should be setting it anyway).

This is documented somewhat obliquely by the "[Pick one]" prefix in the field descriptions here:
https://cloud.google.com/bigquery/docs/reference/v2/datasets

@dhermes
Copy link
Contributor Author

dhermes commented Jan 1, 2016

Thanks @jcondit!

@dhermes
Copy link
Contributor Author

dhermes commented Jan 9, 2016

@jcondit Thanks I finally got the fix out. It seems

https://cloud.google.com/bigquery/access-control#datasetroles

could be updated to be more in line with

https://cloud.google.com/bigquery/docs/reference/v2/datasets

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the BigQuery API.
Projects
None yet
Development

No branches or pull requests

3 participants