-
Notifications
You must be signed in to change notification settings - Fork 4.6k
[Java] Honor withMaxRetryJobs for bounded BigQueryIO file loads #39938
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
Open
mxtymoshyk
wants to merge
2
commits into
apache:master
Choose a base branch
from
mxtymoshyk:bq-max-retry-jobs-bounded
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
could this preserve old bounded default when rebuilding a write from a legacy config row? older versions always serialized
max_retry_jobs=1000, even whenwithMaxRetryJobs()was never called.fromConfigRow()restores that non-null value, so this branch appears to treat it as explicit and could change boundedFILE_LOADSretries from 3 to 1000.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.
Good catch, you're right. Before this change
BigQueryIO.write()seeded the builder with.setMaxRetryJobs(1000), sotoConfigRowwrote 1000 into every row whether or not the pipeline ever calledwithMaxRetryJobs(). The new code reads any non-null value as an explicit request, so a batchFILE_LOADSpipeline rebuilt from an older row would have gone from 3 retries to 1000.Fixed in
fromConfigRow. A row from before 2.77.0 holding exactly 1000 carries no information about intent, because that was the value either way, so it is now left unset and each mode falls back to the number it used before the upgrade: 3 for bounded, 1000 for unbounded. Any other value was chosen deliberately and is still carried over. Rows from 2.77.0 and later only contain the field when the pipeline set it, so an explicitwithMaxRetryJobs(1000)survives there.Two things worth flagging. A pre-2.77.0 bounded pipeline that did call
withMaxRetryJobs(500)will now get 500 instead of 3, but that is the bug this PR is fixing and it is covered by the CHANGES.md entry. And sincefromConfigRowtreats a missingupdateCompatibilityVersionas 2.53.0, a current pipeline that explicitly asks for 1000 and goes through this path without that option set will also be treated as unset. That affects only the single value 1000, and it matches how the rest of this method already handles version defaults.Added three cases to
BigQueryIOTranslationTestcovering the legacy 1000, a legacy value that is not a default, and a 2.77.0 row. I checked they fail if the new guard is removed.