udf_metadata

Full reference: paidteam-data-warehouse.customer_ads_suse.udf_metadataType: Metadata | Rows: 10 | Size: < 0.1 MB

Tracks all User-Defined Function (UDF) versions in the data warehouse. Each UDF change is logged here with version number, author, and change notes. Used for auditing and debugging when UDF behavior changes affect downstream views and dashboards.

Schema

Column	Type	Nullable	Description
udf_name	STRING	Yes	Name of the UDF (e.g., get_content_name, get_region)
version	STRING	Yes	Version string (e.g., "1.0", "1.1", "2.0")
updated_at	TIMESTAMP	Yes	Timestamp of the version change
updated_by	STRING	Yes	Author who made the change
notes	STRING	Yes	Description of what changed in this version

Partitioning & Clustering

• Partitioned by: None
• Clustering: None

Usage

View All UDF Versions

SELECT *
FROM `paidteam-data-warehouse.customer_ads_suse.udf_metadata`
ORDER BY udf_name, updated_at DESC;

Check Latest Version of a Specific UDF

SELECT *
FROM `paidteam-data-warehouse.customer_ads_suse.udf_metadata`
WHERE udf_name = 'get_content_name'
ORDER BY updated_at DESC
LIMIT 1;

Log a New UDF Version

INSERT INTO `paidteam-data-warehouse.customer_ads_suse.udf_metadata`
  (udf_name, version, updated_at, updated_by, notes)
VALUES
  ('get_content_name', '1.2', CURRENT_TIMESTAMP(), 'your_name',
   'Added handling for Thought Leadership creatives');

Notes

• This table serves as a changelog for UDFs. It does not enforce uniqueness -- multiple rows for the same UDF represent its version history.
• UDF changes can be breaking if they alter return types or parameter signatures. Always check this table before modifying UDF-dependent views.
• The notes column should describe the "why" of the change (e.g., "Added platform parameter to support LinkedIn segment extraction") rather than just the "what".
• Currently tracks 10 UDF version entries across all UDFs in the warehouse.
• When creating or updating a UDF, always insert a corresponding row into this table as part of the same deployment.