-
Notifications
You must be signed in to change notification settings - Fork 127
feat(bigquery): Support Fine Grained ACLs for Datasets #3803
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments about the enum definitions, but LGTM otherwise. Thanks for putting this together!
google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/BigQuery.java
Outdated
Show resolved
Hide resolved
google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/BigQuery.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one other minor thing: do we want to document the default _UNSPECIFIED enum values? I'm fine either way.
The _UNSPECIFIED enum value seems a bit redundant to me, since the proto definition says that it will just default to FULL if unspecified. What do the other languages do here? |
This is a manifestation of https://google.aip.dev/126 which specifies the default (0 value) enum handles the unspecified case. It's a way of explicitly stating "use the service's default" value, which is documented as meaning "full" today but could potentially change in the future. |
This PR adds the options dataset_view and update_mode to the get and patch dataset requests respectively. These new options decide whether the metadata and or ACL information should be checked when retrieving or updating a dataset.