Connect to BigQuery
Connect to BigQuery with your gcloud login, Application Default Credentials, a service account key or workload identity federation.
Tablyne connects to BigQuery over its REST API. You choose a billing project and a way to sign in. The test button checks the sign-in and does not run a query.
Ways to sign in
- gcloud login. Uses the account from
gcloud auth loginon this machine. - Application Default Credentials (ADC). Uses the credentials from
gcloud auth application-default login, or a user credential file named byGOOGLE_APPLICATION_CREDENTIALS. - Service account key (JSON). Paste the JSON or import the file. Tablyne checks the type, client email, private key and token URI. The key goes to the system vault, and the screen shows only the account email.
- Workload identity federation. Use the
external_accountconfiguration that gcloud generates, with the external token in a file. URL, program and AWS credential sources are not supported.
You can also set a service account to impersonate. Queries then run as that account, and your login needs the Service Account Token Creator role on it.
Access tokens stay in memory. A key or federation file goes only to the system vault, never to the connections file or to exports.
Project, dataset and location
The billing project is the project charged for queries. You can still read other projects by their full name, and you can pin projects in the tree, including public data. A default dataset is optional. The job location, such as US, EU or southamerica-east1, is optional too. When it is empty, BigQuery works it out.
Cost settings
Set the per-query cap in GiB and your price per TiB. Choose on-demand billing, or capacity billing, where the console shows bytes and slot time instead of dollars.