Area: Ingestion
Sub-Area: BigQuery
Issue
BigQuery ingestion is extracting datasets from incorrect or unintended projects, or filtering configuration is not working as expected to limit which projects/datasets are ingested into DataHub.
Solution
Note: For DataHub Cloud customers, infrastructure-level changes are managed by DataHub Support.
- Configure project filtering:
source:
type: bigquery
config:
project_id: "your-main-project"
# Explicitly list allowed projects
project_ids:
- "analytics-prod"
- "data-warehouse"
# Or use patterns
project_id_pattern:
allow: ["prod-.*", "analytics-.*"]
deny: ["test-.*", "dev-.*", ".*-sandbox"]
Verify service account permissions:
- Ensure the service account only has BigQuery Data Viewer role on intended projects
- Remove permissions from unwanted projects
- Use
project_idslist instead of patterns for precise control
Troubleshoot unexpected projects:
- Check if service account was granted organization-level permissions
- Review BigQuery audit logs to see which projects the service account accessed
- Use
include_table_lineage: truewith caution as it scans query logs across accessible projects
Test with single project first:
- Start with one
project_idto confirm filtering works - Gradually add more projects using
project_idslist - Verify in DataHub UI that only intended datasets appear
- Start with one
Additional Notes
Test configurations in a development environment before applying to production. Always backup configurations before making changes.
Related Documentation
Related Tickets
- 5692, 5643, 5606
Tags:
bigquery, project-filtering, gcp, troubleshooting