BigQuery usage docs do not explain references
See original GitHub issueThe BigQuery usage docs do not explain what TableReference
s are, when/why you’d need to use one instead of a Table
, and how to get a TableReference
from a Table
or vice versa.
(And similarly for DatasetReference
s and Dataset
s.)
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Query syntax | BigQuery - Google Cloud
You may reference columns in a table passed to PIVOT , as well as correlated columns, but may not access columns defined by...
Read more >BigQuery setup - dbt Developer Hub
This connection method requires local OAuth via gcloud . ... If you do not specify a project / database and are using the...
Read more >bigquery - Go Packages
These methods create references to datasets, not the datasets themselves. You can have a dataset reference even if the dataset doesn't exist yet....
Read more >The Lazy Guide to Learning BigQuery SQL
At the top of the query, you can define each table you'll use, and do any filtering + grouping beforehand. Then, when you...
Read more >Google BigQuery I/O connector - Apache Beam
To specify a BigQuery table, you can use either the table's ... BigQuery data types: // https://cloud.google.com/bigquery/docs/reference/ ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Re: my previous comment.
I’ve sent https://github.com/GoogleCloudPlatform/google-cloud-python/pull/5255 to add
Dataset/Table.from_string(fully_qualified_id)
, which I think will address the concern that it requires too many objects to create a table/dataset.Honestly since the REST API separates everything out like
it hadn’t crossed my mind to accept a fully-qualified dataset ID. I would be open to a PR that modifies Dataset to accept strings like “project.dataset” as an option where there is a Dataset reference.