-
Notifications
You must be signed in to change notification settings - Fork 68
feat: handle auto pagination for BigQuery v2 #3829
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
base: main
Are you sure you want to change the base?
Conversation
I'm unsure which checks are relevant/needed. Please let me know, |
/gcbrun |
PAGINATE_MAX_RESULT_TYPES = | ||
ImmutableMap.of( | ||
"com.google.cloud.bigquery.v2", | ||
ImmutableMap.of( |
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 guess there are some legacy RPCs use max_results
field and are not of wrapper types?
// This is similar to the PagedExpand except that it uses | ||
// max_results instead of page_size, as some legacy APIs still | ||
// do. New APIs should NOT use this pattern. | ||
rpc PagedExpandLegacy(PagedExpandLegacyRequest) returns (PagedExpandResponse) { |
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 don't think this test can prove much because the package is not bigquery, this is more like a negative test case which is already covered by other test cases. We need a positive golden test file that can demonstrate the changes.
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.
Are golden tests for this file missing?
Thank you for opening a Pull Request! Before submitting your PR, please read our contributing guidelines.
There are a few things you can do to make sure it goes smoothly:
Fixes # b/360114900 & b/352331075