Use strings instead of reference objects in google-cloud-bigquery notebook #2
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
Ideally, DatasetReference and TableReference won't be necessary to create. Already for most use cases they are optional.
Also, use not_found_ok when deleting datasets/tables and exists_ok when creating datasets/tables.
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.
Simplify the notebook to remove the need for explicit
TableReferenceorDatasetReferenceobjects. Also, we're able to delete a lot of helper code with the newnot_found_okandexists_okparameters.Depends on
google-cloud-bigquery==1.10.0. Release pending at googleapis/google-cloud-python#7497