feat: Allow loading a DataFrame even if the provided BigQuery schema includes columns not in the DataFrame #953
+33
−13
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.
This change modifies the behavior when a DataFrame is loaded to BigQuery with a schema that contains fields not present in the DataFrame.
Instead of raising a
ValueError, aUserWarningis now issued, and the extra fields are appended to the schema. This allows for more flexible data loading scenarios.CONTEXT: this was originally a suggestion for the
python-bigquerylibrary and we made the decision to move it here since we are deprecating that corresponding function inpython-bigquery. That suggestion was found in the followingpython-bigqueryIssue:Fixes googleapis/python-bigquery#1812 🦕