Connector Lifecycle
What happens if I delete a connector?
What happens if I delete a connector?
Deleting a source triggers an approval workflow based on your organization’s settings. Once approved, the source and all associated metadata are permanently deleted. The deletion cannot be undone after approval.
What happens to existing data and alerts if a connector is paused or disconnected?
What happens to existing data and alerts if a connector is paused or disconnected?
Existing metadata, quality scores, and alerts are retained while the connector is inactive. No new data is collected until the connector is re-enabled. If the connector is permanently deleted (after approval), all associated data is removed.
BigQuery-Specific
Which authentication methods are supported?
Which authentication methods are supported?
A service account key (JSON file, uploaded or retrieved from a vault) and Workload Identity. Workload Identity appears on the connection form but hasn’t been verified end to end, so use a service account key. See Setup.
Which APIs do I need to enable?
Which APIs do I need to enable?
BigQuery, Data Lineage, Dataplex, Data Catalog, Cloud Resource Manager, IAM Service Account Credentials, and Security Token Service. Enable them in the host project, and enable the Data Lineage API in every project where jobs run. See Setup.
Which roles does Prizm need?
Which roles does Prizm need?
It depends on what you want extracted. Metadata needs
roles/bigquery.metadataViewer and roles/bigquery.jobUser; usage and job-log lineage need roles/bigquery.resourceViewer; Data Lineage API lineage needs roles/datalineage.viewer; tags need the tag and catalog viewer roles. See the full table in Setup.Why is there no lineage for jobs that ran before I connected?
Why is there no lineage for jobs that ran before I connected?
The Data Lineage API records lineage only from the moment it is enabled in a project, and it doesn’t backfill earlier jobs. If you need history from before that, set Lineage Mode to Job Logs, which reads source and destination tables from earlier jobs. Enable the Data Lineage API as early as possible.
Which lineage mode should I choose?
Which lineage mode should I choose?
Use Via DataPlex API (the default) when the Data Lineage API is enabled in the projects where your jobs run. Use Job Logs if you can’t enable the API or you need earlier history. Job logs are weaker for DML targets and view-to-table links. You choose one mode per connection, and column-level lineage isn’t covered yet.
Why is lineage missing for a particular location?
Why is lineage missing for a particular location?
The Data Lineage API is regional. Set GCP Region / Location to the location your jobs run in, and make sure the API is enabled in the project where those jobs run.
What do I need for organization-wide usage data?
What do I need for organization-wide usage data?
JOBS_BY_ORGANIZATION requires roles/bigquery.resourceViewer at the organization level. For per-project usage data, grant the role on each project instead.Does Prizm change anything in BigQuery?
Does Prizm change anything in BigQuery?
No. The roles Prizm needs are read-only for metadata and job history.
Troubleshooting
For connection errors, permission issues, and performance problems.
Glossary
For definitions of terms used in this FAQ.