Cloudera Docs

Product Release Notes - June 2026

Cloudera Data Lineage extends connector coverage for Microsoft Fabric and file-based lineage, including non-SQL code analysis, GitHub-backed metadata sources, and source SQL parsing in Custom Lineage templates.

Overview

Cloudera Data Lineage now supports automatically harvesting metadata from additional Microsoft Fabric tools, native GitHub integration for file-based lineage connectors, and enhanced Custom Lineage Connector source SQL parsing for inner-system lineage in Database, ETL, and Reporting templates, with transformation visualization.

Microsoft Fabric integration

Cloudera Data Lineage expands Microsoft Fabric coverage with connectors for SQL Database, Warehouse, and Lakehouse [Technical Preview], alongside the existing Power BI (Microsoft Fabric) connector. You can map end-to-end lineage across Fabric data repositories, downstream reports, and connected systems in a single view, assess downstream impact before schema changes, and maintain visibility when migrating from legacy Microsoft platforms to Fabric.

  • Power BI (Microsoft Fabric): Trace workspace and report lineage to see how analytics outputs connect to upstream Fabric data assets.

  • SQL Database (Microsoft Fabric) [Technical Preview]: Catalog database objects and relationships to support discovery, governance, and cross-system lineage.

  • Warehouse (Microsoft Fabric) [Technical Preview]: Track warehouse schema and object lineage to evaluate how changes affect Power BI dashboards and other downstream consumers.

  • Lakehouse (Microsoft Fabric) [Technical Preview]: Follow lineage across Lakehouse tables, OneLake files and folders, and shortcuts to understand how lakehouse data flows to reports and dependent systems.

Custom and file-based lineage connectors

  • Custom Lineage Connector — source SQL parsing and inner-system lineage: The ETL, Database, and Reporting CSV templates now support the Source Sql field. Cloudera Data Lineage parses the SQL, breaks down source columns, reflects transformations, and shows derived assets across lineage, Discovery, and the Knowledge Hub, similar to natively supported tools.

  • Code-Based Lineage Connector: Upload Python and Scala files to include non-SQL code in automated data lineage analysis. Configure a metadata source from a Local Folder or Github Folder.

  • GitHub harvesting: Harvest metadata directly from GitHub repositories without copying files to a local folder. This option applies to the Folder connector, Custom Lineage Connector, and Code-Based Lineage Connector (Python and Scala).

Conclusion

These updates extend connector coverage across Microsoft Fabric, custom and file-based lineage workflows. They also strengthen native harvesting, give you more flexibility to ingest metadata from sources that are not natively supported, and expand connectivity options for source files and folders.

For more information, see Power BI (Microsoft Fabric), Code-Based Lineage Connector, and Custom Lineage Connector overview.