dbt Gen2 OCF Connector Release Notes¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
May 14, 2025¶
dbt Gen2 OCF Connector (Beta): Version 1.2.3¶
Enhancements¶
Support for Oracle Data Source¶
dbt Core now supports metadata and lineage extraction from the Oracle data source. (AL-187052)
Fixed Issues¶
Unable to View Source System Information and Lineage for Databricks Unity Catalog in dbt Cloud¶
When you run metadata and lineage extraction for Databricks Unity Catalog source in dbt Cloud, the Source System Information is not displayed in the catalog page. Similarly, lineage information is also not generated.
This issue is now resolved. (AL-184692)
Unable to View Source Comment for Model Columns in dbt Core¶
When you run metadata extraction in dbt Core, the Source Comment information for model columns is not displayed in the catalog page.
This issue is now resolved. (AL-184925)
March 19, 2025¶
dbt Gen2 OCF Connector (Beta): Version 1.1.0¶
Enhancements¶
Support for dbt Core¶
The dbt Gen2 OCF connector now supports dbt Core. The connector extracts projects, models, model columns, and job runs (jobs executed for a given model in an instance) from dbt Core.
The connector supports the following authentication methods:
Amazon S3
GitHub
Azure Blob Storage
For details, see dbt Gen2 OCF Connector. (AL-182071)
March 06, 2025¶
dbt Gen2 OCF Connector (Beta): Version 1.0.3¶
Enhancements¶
Improved Error Messages¶
Alation has improved the error messages for clarity in cases where MDE results in partial success due to missing resources or permission errors. (AL-184360)
Fixed Issues¶
Metadata Extraction and Lineage Extraction Fails¶
MDE and lineage extraction fail intermittently, as the DBT Cloud Admin/Discovery API returns an HTTP 502 error. This is a known issue in DBT Cloud.
However, Alation tries to handle this issue by retrying to call the API again when the connector encounters this issue. The max retry limit is five. (AL-184305)
February 05, 2025¶
dbt Gen2 OCF Connector: Version 1.0.1¶
Fixed Issues¶
Connector Operations Fail Due to Incorrect dbt API Response¶
Test Connection, Metadata Extraction, and Lineage extraction fail because a dbt API returns unexpected output.
This issue is now resolved. (AL-183296)