You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:19:51 UTC
Re: [D] Missing Project ID on BigQuery [superset]
GitHub user dosubot[bot] edited a comment on the discussion: Missing Project ID on BigQuery
<!-- Greeting -->
Hello @esgungor! I'm [Dosu](https://dosu.dev), here to help you with any bugs, questions, or contributions you may have while we wait for a human maintainer. Let’s tackle this together!
<!-- Answer -->
To address the issue of missing project IDs in SQL queries for cross-project access in BigQuery when using Superset, you can configure the connection to include the project ID in the SQLAlchemy URI. Here's how you can do it:
1. **Install the SQLAlchemy BigQuery Driver**: Ensure you have the `sqlalchemy-bigquery` driver installed. You can add it to your Docker requirements:
```bash
echo "sqlalchemy-bigquery" >> ./docker/requirements-local.txt
```
2. **Service Account Setup**: Create a service account in Google Cloud Platform, grant it access to the necessary BigQuery datasets, and download the JSON configuration file.
3. **Configure the Connection in Superset**: When setting up a new BigQuery connection in Superset, use the SQLAlchemy URI format that includes the project ID:
```
bigquery://{project_id}
```
4. **Secure Extra Configuration**: In the database configuration form in Superset, go to the **Advanced** tab and add a JSON blob to the **Secure Extra** field with the following format:
```json
{
"credentials_info": <contents of credentials JSON file>
}
```
This setup should help ensure that the project ID is included in SQL queries, allowing for successful cross-project access <sup>[[1]](https://github.com/apache/superset/blob/master/docs/docs/configuration/databases.mdx)</sup>.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=ba3777e7-349b-4047-a2e2-0a544eda07b6) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33464#discussioncomment-13167992
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org