Google BigQuery
Connect Google BigQuery to Lakehousecat using a GCP Service Account. BigQuery does not use a connection URI — authentication is handled via a Service Account JSON key file.
Connection Fields
| Field | Required | Description |
|---|---|---|
| Credentials JSON | Yes | Service Account key file in JSON format. Download it from the GCP Console under IAM & Admin → Service Accounts → Keys. |
| Project ID | Yes | GCP project ID where BigQuery is running |
| Dataset ID | No | Restrict access to a specific dataset. If left empty, all datasets in the project are loaded. |
GCP Service Account Requirements
The Service Account must have the following minimum IAM roles:
roles/bigquery.dataViewer— read access to tables and datasetsroles/bigquery.jobUser— permission to run queriesroles/bigquery.metadataViewer— access to dataset and table metadata
Notes
- SSH Tunnel: not supported
- Connection is made via the BigQuery Python SDK, not a JDBC/ODBC URI
- If no Dataset ID is specified, all datasets in the project are accessible
Next Steps
After creating the datasource, go to the Operations tab to trigger semantic extraction.