BigQuery adapter
The BigQuery warehouse adapter runs your SQL through the BigQuery REST API.
Fields
Section titled “Fields”| Field | Type | Required | Description |
|---|---|---|---|
project_id |
string | No | Google Cloud project ID that owns the datasets and is billed for query execution. |
location |
string | No | BigQuery processing location (e.g., "US", "EU", "us-central1"). |
[adapter.bq]type = "bigquery"project_id = "${GCP_PROJECT_ID}"location = "US"Authentication
Section titled “Authentication”Rocky reads BigQuery credentials from the environment, never from rocky.toml. It checks two variables in this order.
BIGQUERY_TOKEN— an OAuth bearer token you obtained yourself. Rocky uses it as is. Because Rocky checks it first, setting it overrides any service-account key on the same machine.GOOGLE_APPLICATION_CREDENTIALS— the path to a service-account JSON key. Rocky mints a JWT from the key, exchanges it for an access token at Google’s token endpoint, and refreshes the token before it expires.
If neither variable is set, the adapter fails with no authentication method available — set GOOGLE_APPLICATION_CREDENTIALS or provide a bearer token.
See also
Section titled “See also”[adapter.NAME]— fields shared by every adapter type, including the retry policy.