BigQuery copy method can convert dict column to JSON string #1143
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
KasiaHinkson
approved these changes
Oct 8, 2024
By default without this change, a dict column will cause the copy method to fail.
austinweisgrau
force-pushed
the
bq_copy_dict
branch
from
c7b376b to
7ce3800
Compare
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.
By default without this change, a dict column will cause the copy method to fail.
This is a more robust followup to #1028 and #1068. At the time we decided to remove support for loading dict columns to BigQuery because there wasn't a super simple way to accomplish this. Instead we encouraged users to convert the dict columns to strings themselves if they desired to do so. This change makes that workaround happen by default, but it can be turned off with the
convert_dict_columns_to_jsonflag toBigQuery().copy()