Skip to content

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

Merged
merged 4 commits into from
May 30, 2025
Merged

feat(bigquery): Support Fine Grained ACLs for Datasets #3803

merged 4 commits into from
May 30, 2025

Conversation

whuffman36
Copy link
Contributor

@whuffman36 whuffman36 commented May 28, 2025

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.

@product-auto-label product-auto-label bot added size: m Pull request size is medium. api: bigquery Issues related to the googleapis/java-bigquery API. labels May 28, 2025
@whuffman36 whuffman36 marked this pull request as ready for review May 28, 2025 17:41
@whuffman36 whuffman36 requested a review from a team as a code owner May 28, 2025 17:41
@whuffman36 whuffman36 requested review from mrfaizal, shollyman and alvarowolfx and removed request for mrfaizal May 28, 2025 17:41
shollyman
shollyman previously approved these changes May 28, 2025
Copy link
Contributor

@shollyman shollyman left a 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!

shollyman
shollyman previously approved these changes May 28, 2025
Copy link
Contributor

@shollyman shollyman left a 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.

@whuffman36
Copy link
Contributor Author

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?

@shollyman
Copy link
Contributor

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.

@whuffman36 whuffman36 merged commit bebf1c6 into main May 30, 2025
22 checks passed
@whuffman36 whuffman36 deleted the acl branch May 30, 2025 21:18
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 googleapis/java-bigquery API. size: m Pull request size is medium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants