-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add data clean rooms support #11067
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
Add data clean rooms support #11067
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @shuyama1, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
1 similar comment
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
Action takenFound 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
1 similar comment
Tests analyticsTotal tests: 12 Click here to see the affected service packages
Action takenFound 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
|
@shuyama1 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
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.
Hey @obada-ab, I assume the PR is still WIP, so I added the disable-review-reminders
label to avoid generating noise to this PR. Please feel free to let me know if you have any questions regarding the change in this PR/ when the PR is ready for review. Thanks!
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
@@ -151,6 +164,7 @@ properties: | |||
name: bigqueryDataset | |||
description: Shared dataset i.e. BigQuery dataset source. | |||
required: true | |||
immutable: true |
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.
Do you happen to know what's current behavior if a user is trying to update this field? Will it error out?
Making the field immutable may break users depends on how the update of the field is handled currently.
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.
I tried updating the field before making this change and got an error:
Error: Error updating Listing "projects/X/locations/US/dataExchanges/Y/listings/Z": googleapi: Error 400: The field 'bigquery_dataset' cannot be updated on this listing.
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.
Thanks for confirming! Then, it should be safe to make this change in a minor release as update is not currently supported for this field and will run into API errors in all cases, according to https://googlecloudplatform.github.io/magic-modules/develop/breaking-changes/make-a-breaking-change/#in-minor-releases
/gcbrun |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
View the build log |
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.
Mostly LGTM. got one question though - Do any of these fields updatable? I notice some immutable flags are on the parent fields but not on the subfields, so I just want to confirm. If any of these are updatable, would you mind following https://googlecloudplatform.github.io/magic-modules/develop/test/test/#add-an-update-test to either add a new test or modify an existing one to cover these cases?Thanks!
All the added fields are either immutable or output only. I believe it's enough to have the immutable flag on the parent fields, because all subfields will also be immutable (reference) |
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.
All the added fields are either immutable or output only. I believe it's enough to have the immutable flag on the parent fields, because all subfields will also be immutable (reference)
Thanks for confirm that all the fields are immutable. I just had a discussion with my team and we agree that the documentation needs to be updated - Each immutable subfield must have the immutable attribute explicitly added, even if the parent field is already marked as immutable.
Would you mind adding immutable:true
to all the immutable subfields as well? Apologize for the confusion in the doc and thanks for working on this.
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
View the build log |
Tests analyticsTotal tests: 12 Click here to see the affected service packages
View the build log |
/gcbrun |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
|
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.
Thank you!
API:
Guide: https://cloud.google.com/bigquery/docs/data-clean-rooms
Reference: b/347844459
Release Note Template for Downstream PRs (will be copied)