Denodo - Lineage
This article outlines the lineage coverage, configuration settings, metadata handling, supported scenarios, component behaviors, process flow, and known gaps for lineage extraction in Denodo. The lineage process captures how data flows across virtual views, underlying source systems, and file-based wrappers by utilizing lineage metadata available within Denodo. It supports both table-level and column-level lineage to provide visibility into data movement and transformations across datasets.
Lineage Configuration Requirements
Accurate lineage extraction depends on appropriate access permissions and correct configuration settings. The connection must have access to Denodo datasets and lineage metadata payloads with permissions to read views, source objects, and column mappings. For complete lineage extraction, dataset query metadata must be available and include source-to-target column mappings. Proper configuration of connection priorities also helps resolve source systems accurately.
Configuration Requirements Table
Query Metadata Availability
Dataset query metadata must be available and include source-to-target column mappings for complete lineage extraction
Connection Priority Configuration
Proper configuration of connection priorities helps resolve source systems accurately
Metadata Permissions
Appropriate permissions are required to access lineage-related metadata objects
Column Mapping Availability
Column-level lineage depends on the availability of source-to-target column mapping metadata
Missing permissions, unavailable metadata, or an incorrect connection-priority configuration may result in incomplete lineage extraction.
Lineage Components
Tables
✅
Views (Derived/Interface)
✅
Columns
✅
JDBC Sources
✅
File Wrappers
✅
SQL Queries (sqlsentence)
⚠️
Procedures/Functions
⚠️
JSON/API Wrappers
⚠️
SAP Sources
⚠️
Temporary Objects
⚠️
Unsupported Datasources
❌
Direct Column Mapping
✅
Alias Mapping
✅
Expressions
⚠️
Aggregations
⚠️
Derived Columns
⚠️
Temp Columns
⚠️
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
Supported Use Cases
The connector supports several datasets and visualization lineage scenarios across different components of Denodo. These use cases describe areas where lineage extraction functions as expected.
Supported Lineage Scenarios
Denodo View to Source Table Lineage
Lineage extraction from Denodo views to the underlying source tables
Table to Table Lineage
Lineage mapping between source and target tables
File to Table Lineage
Lineage extraction from file-based sources to tables
Column to Column Lineage
Column-level source-to-target lineage mapping
Derived or View Dependency Lineage
Lineage for derived objects and dependent views
SQL-Based Lineage
SQL parsing and lineage extraction from query logic
Column-level lineage and dependency mapping depend on the availability of lineage metadata and query parsing support.
Partial or Limited Coverage
Certain scenarios function only with partial coverage due to limitations in metadata, query formats, or processing complexity. These areas may produce incomplete lineage results.
Scenarios
SQL-Based Lineage
Complex queries may have limited parsing support
Derived Columns
Expression-level lineage depends on metadata availability
Aggregations
Limited support for complex transformations
JSON or API Wrappers
Supported only for specific wrapper patterns
Procedures or Functions
Partial support based on metadata discovery
Temporary Objects
May result in partial lineage extraction
Incomplete metadata or encrypted data sources can prevent lineage creation entirely.
Unsupported Scenarios
The connector does not support lineage extraction for certain components and modeling features due to the absence of accessible metadata or non-SQL-based logic.
Unsupported Lineage
Certain Datasource Types
Unsupported datasource types are not included in lineage extraction
Complex Dynamic SQL Patterns
Dynamic or parameterized SQL patterns are not fully resolved
Advanced Transformation Logic
Complex transformation logic without explicit mappings is not supported
Non-Supported Wrapper Types
Unsupported wrapper types are excluded from lineage processing
Missing or Incomplete Lineage Metadata
Lineage cannot be generated when required metadata is unavailable or incomplete
Unsupported scenarios will not produce lineage and may appear disconnected in lineage visualization.
Current Functional Status
This section outlines the present state of lineage coverage supported by the Denodo connector based on the available capabilities and limitations.
Current Status
Provides strong lineage support for Denodo views, JDBC sources, and file-based wrappers with column-level mapping when metadata is available
Coverage Areas
Coverage is limited for unsupported data source types, complex SQL logic, and scenarios without detailed lineage metadata
Lineage Support
Supports table-level and column-level lineage extraction for supported objects
Metadata Dependency
Accurate lineage extraction depends on the availability of complete lineage metadata
Limitation Areas
Advanced SQL patterns and unsupported wrapper types may result in partial lineage coverage
Resulting Output
Lineage is generated for supported scenarios, with partial mapping in unsupported or metadata-limited cases
Coverage is limited for unsupported data source types, complex SQL logic, and scenarios lacking detailed lineage metadata.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?