-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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 Storage API streaming max retries parameter for BigQueryOptions #31683
Conversation
R: @Abacn |
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control |
multiple band-aid fix has made the retry behavior more complicated. Specifically, for batch job, the max retry number is not longer to be 500 #26503 - fail the work item after retry 5 times, in StorageApiWriteUnshardedRecords, this is for batch #31253 - retry 10 times (instead of 5) for quota error and this change works for streaming (which uses StorageApiWritesShardedRecords or StorageApiWriteRecordsInconsistent) Let's update the description mention that this is only for streaming, or update to make it also work with batch (but need more care, batch and streaming currently have different default) |
Run Java_GCP_IO_Direct PreCommit |
d6b1177
to
accd19e
Compare
I renamed the parameter and description |
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.
When we come back to the batch pipeline retry it's good to not introducing another pipeline option. How about keep getStorageWriteApiMaxRetries
naming and in the description noting that currently it is only applicable for streaming pipeline?
Or noting in javadoc that this opition is experimental and could change?
accd19e
to
cd88a83
Compare
Agree, fixed |
Fixes #25382
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.