-
Notifications
You must be signed in to change notification settings - Fork 122
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
feat: map "if_exists" value to LoadJobConfig.WriteDisposition #583
Conversation
…orage version to 2.16.2, and pydata-google-auth version to 1.4.0
This reverts commit ad45c6d.
@tswast are the version bumps/PR description added to the Changelog automatically? |
No, that needs to be included in the commit message when we 'squash and merge'. See: https://github.com/googleapis/release-please#what-if-my-pr-contains-multiple-fixes-or-features |
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.
Thanks for putting this together. Switching to leveraging write disposition cleans things up nicely.
Use
LoadJobConfig.WriteDisposition
to replaceif_exists='fail'/'replace'/'append'
behavior into_gbq()
The WriteDisposition value specifies the action that occurs if destination table already exists.
By using WriteDisposition, we can move away from the
delete_and_recreate_table()
behaviorFixes #118 #43 #453