> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/connectors/connector-repositories/rdbms/denodo/denodo-lineage.md).

# 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

<table><thead><tr><th width="284.22216796875">Configuration</th><th>Required Detail</th></tr></thead><tbody><tr><td>Query Metadata Availability </td><td>Dataset query metadata must be available and include source-to-target column mappings for complete lineage extraction </td></tr><tr><td>Connection Priority Configuration </td><td>Proper configuration of connection priorities helps resolve source systems accurately </td></tr><tr><td>Metadata Permissions </td><td>Appropriate permissions are required to access lineage-related metadata objects </td></tr><tr><td>Column Mapping Availability </td><td>Column-level lineage depends on the availability of source-to-target column mapping metadata </td></tr></tbody></table>

{% hint style="warning" %}
Missing permissions, unavailable metadata, or an incorrect connection-priority configuration may result in incomplete lineage extraction.
{% endhint %}

## Lineage Components

| Component                 | Availability |
| ------------------------- | :----------: |
| 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              |      ⚠️      |

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
{% endhint %}

## 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

| Supported                           | Details                                                              |
| ----------------------------------- | -------------------------------------------------------------------- |
| 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                  |

{% hint style="info" %}
Column-level lineage and dependency mapping depend on the availability of lineage metadata and query parsing support.
{% endhint %}

## 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

<table><thead><tr><th width="227.3333740234375">Scenario</th><th>Limitation Description</th></tr></thead><tbody><tr><td>SQL-Based Lineage</td><td>Complex queries may have limited parsing support</td></tr><tr><td>Derived Columns</td><td>Expression-level lineage depends on metadata availability</td></tr><tr><td>Aggregations</td><td>Limited support for complex transformations</td></tr><tr><td>JSON or API Wrappers</td><td>Supported only for specific wrapper patterns</td></tr><tr><td>Procedures or Functions</td><td>Partial support based on metadata discovery</td></tr><tr><td>Temporary Objects</td><td>May result in partial lineage extraction</td></tr></tbody></table>

{% hint style="warning" %}
Incomplete metadata or encrypted data sources can prevent lineage creation entirely.
{% endhint %}

## 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

<table><thead><tr><th width="332.22216796875">Not Supported</th><th>Description</th></tr></thead><tbody><tr><td>Certain Datasource Types</td><td>Unsupported datasource types are not included in lineage extraction</td></tr><tr><td>Complex Dynamic SQL Patterns </td><td>Dynamic or parameterized SQL patterns are not fully resolved </td></tr><tr><td>Advanced Transformation Logic </td><td>Complex transformation logic without explicit mappings is not supported </td></tr><tr><td>Non-Supported Wrapper Types </td><td>Unsupported wrapper types are excluded from lineage processing </td></tr><tr><td>Missing or Incomplete Lineage Metadata </td><td>Lineage cannot be generated when required metadata is unavailable or incomplete </td></tr></tbody></table>

{% hint style="info" %}
Unsupported scenarios will not produce lineage and may appear disconnected in lineage visualization.
{% endhint %}

## Current Functional Status

This section outlines the present state of lineage coverage supported by the Denodo connector based on the available capabilities and limitations.

<table><thead><tr><th width="206.88873291015625">Status Area</th><th>Details</th></tr></thead><tbody><tr><td>Current Status </td><td>Provides strong lineage support for Denodo views, JDBC sources, and file-based wrappers with column-level mapping when metadata is available </td></tr><tr><td>Coverage Areas </td><td>Coverage is limited for unsupported data source types, complex SQL logic, and scenarios without detailed lineage metadata </td></tr><tr><td>Lineage Support </td><td>Supports table-level and column-level lineage extraction for supported objects </td></tr><tr><td>Metadata Dependency </td><td>Accurate lineage extraction depends on the availability of complete lineage metadata </td></tr><tr><td>Limitation Areas </td><td>Advanced SQL patterns and unsupported wrapper types may result in partial lineage coverage </td></tr><tr><td>Resulting Output </td><td>Lineage is generated for supported scenarios, with partial mapping in unsupported or metadata-limited cases </td></tr></tbody></table>

{% hint style="info" %}
Coverage is limited for unsupported data source types, complex SQL logic, and scenarios lacking detailed lineage metadata.
{% endhint %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/rdbms/denodo/denodo-lineage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.