馃尡 Use a completion threshold for BQ transfers #930
Merged
Conversation
This file contains 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
|
Integration tests success for 02ae835c5d18e84b09b671e57fae22851450fc0f |
azeemshaikh38
force-pushed
the
azeems/transfer
branch
from
02ae835
to
46835eb
Compare
|
Integration tests success for 46835eb2dec92ce7cf9589915f143d8c3348d094 |
oliverchang
approved these changes
Aug 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
To allow for some shard failures, use a completion threshold instead of equality to start a BQ transfer job.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.