Bigquery Integration Discovered Resources
The Euno-BigQuery integration discovers the following resources:
BigQuery Project
name
The GCP project's display name
native_id
The GCP project's id
type
always gcp_project
Only GCP projects with views or tables are discovered
BigQuery Dataset
name
The GCP dataset's name
description
The dataset's description, if available
created_at
updated_at
parent container
The GCP project containing the dataset
type
always gcp_dataset
meta
Any dataset label will be observed as a meta entry
Table
name
The GCP view's name
subtype
base table, view, or materialized view
description
The view's description, if available
created_at
updated_at
parent container
The GCP dataset containing the view
type
always table
materialized
for tables: true
for views: false
meta
Any view label will be observed as a meta entry
table properties
The SQL definition of the view
table dependencies
The list of views or tables this view depends on based on its SQL definition
database technology
always bigquery
schema
The name of the BigQuery dataset containing the view
database
The name of the GCP Project
Relationships
bigquery dataset
child
bigquery project
table
child
bigquery dataset
column
child
table
table
upstream
table
For views, this is based on analyzing the SQL defining the view. For tables, the lineage is based on analyzing the queries in the log. Euno considers all write queries in the last 7 days to constitue the lineage.
column
upstream_fields
column
For views, this is based on analyzing the SQL defining the view. For tables, the lineage is based on analyzing the queries in the log. Euno considers all write queries in the last 7 days to constitue the lineage.
Known Limitations
For columns of type STRUCT, column-level lineage (upstream_fields relationships) is tracked only at the column level, from the source BigQuery column to the target BigQuery column. Lineage is not captured for individual nested keys within the STRUCT.
Last updated