-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[BEAM-11277] Respect schemaUpdateOptions during BigQuery load with temporary tables #14113
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
Merged
pabloem
merged 10 commits into
apache:master
from
chunyang:cyang/copy-schema-relaxation
Mar 31, 2021
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
d98f1d1
Iterate over temp_tables_pc only once
chunyang 37adbfd
WIP: Update destination table schemas
chunyang de0d90c
Consistency: Use pvalue rather than beam.pvalue
chunyang 91e9a15
Trigger schema update load job using empty file
chunyang 1e25380
Add tests for BigQueryWrapper.perform_load_job
chunyang 911945c
Add integration test
chunyang b20c2cb
Merge remote-tracking branch 'origin/master' into cyang/copy-schema-r…
chunyang 0da0532
Use separate singletons in _load_data
chunyang 6acd291
Avoid running a schema modification load job...
chunyang b9ff38e
Fix spacing
chunyang 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
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.
Does it make sense to compare the schema of the destination table with the schema of the temp table job? We'd save one load, right?
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.
Added a simple comparison of
destination_table.schema == temp_table_schema. It will work for trivial cases but doesn't catch the cases where the order of fields in a record differs. E.g., the following schemas are different according to==even though the temp table can be directly appended to the destination table without error.I can probably write a function to check the schema recursively but do you know if one already exists?