[Data] Expose max_retry_cnt parameter for BigQuery Write #41163
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Matthew Tang <[email protected]>
Signed-off-by: Matthew Tang <[email protected]>
matthew29tang
requested review from
Zandew,
amogkam,
bveeramani,
c21,
ericl,
raulchen,
scottjlee,
scv119 and
stephanie-wang
as code owners
matthew29tang
changed the title
bveeramani
reviewed
Nov 15, 2023
Signed-off-by: Matthew Tang <[email protected]>
Signed-off-by: Matthew Tang <[email protected]>
Signed-off-by: Matthew Tang <[email protected]>
ujjawal-khare
pushed a commit
to ujjawal-khare-27/ray
that referenced
this pull request
Nov 29, 2023
…#41163) Exposing max_retry_cnt to the user will give them more flexibility to increase the number of retries for very large writes that may encounter more rate limit exceptions. --------- Signed-off-by: Matthew Tang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
Exposing max_retry_cnt to the user will give them more flexibility to increase the number of retries for very large writes that may encounter more rate limit exceptions.
Related issue number
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.