> 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/reporting-tool/looker/looker-lineage.md).

# Looker - Lineage

This article outlines lineage coverage, configuration requirements, supported components, transformation support, supported use cases, partial or limited coverage, unsupported scenarios, and the current functional status of lineage extraction in Looker.

The Looker connector provides end-to-end lineage from underlying database tables to Looker Looks and Dashboards. It supports lineage across SQL-based reports and dashboards, including column-level lineage, to provide visibility into data flow and impact analysis. The connector supports static SQL queries, derived tables, merge queries, and supported SQL transformations.

## Lineage Configuration Requirements

Successful lineage extraction depends on valid Looker API access, appropriate permissions, available database metadata, accessible SQL definitions, and correct SQL dialect configuration. The following requirements apply to Looker lineage extraction.

### Configuration Requirements Table

<table data-search="false"><thead><tr><th width="180">Configuration</th><th>Required Detail</th></tr></thead><tbody><tr><td>Authentication</td><td>Valid Looker API credentials and connection setup must be available for metadata extraction.</td></tr><tr><td>Access</td><td>Read access to Looks, Dashboards, and the underlying database must be available.</td></tr><tr><td>Database Metadata</td><td>Database metadata must be crawled before lineage is built so that source tables and columns can be resolved.</td></tr><tr><td>SQL Availability</td><td>SQL queries must be available for lineage generation.</td></tr><tr><td>SQL Dialects</td><td>The appropriate SQL dialect must be configured to support SQL parsing.</td></tr><tr><td>SourceCode</td><td>SQL definitions must be available in <code>SourceCode</code> for lineage generation.</td></tr></tbody></table>

{% hint style="warning" %}
Missing API access, insufficient permissions, unavailable database metadata, inaccessible SQL definitions, or incorrect SQL dialect configuration may result in incomplete lineage generation.
{% endhint %}

## Lineage Components

The following table identifies the Looker components and lineage features handled by the connector.

<table data-search="false"><thead><tr><th>Component / Feature</th><th align="center">Supported</th></tr></thead><tbody><tr><td>Looks</td><td align="center">✅</td></tr><tr><td>Dashboards</td><td align="center">✅</td></tr><tr><td>Dashboard Tiles</td><td align="center">✅</td></tr><tr><td>Merge Queries</td><td align="center">✅</td></tr><tr><td>Static SQL Queries</td><td align="center">✅</td></tr><tr><td>Derived Tables</td><td align="center">✅</td></tr><tr><td>LookML Views / Explores</td><td align="center">⚠️</td></tr><tr><td>Calculated Fields (SQL-based)</td><td align="center">⚠️</td></tr><tr><td>Window Functions</td><td align="center">✅</td></tr><tr><td>Dynamic SQL</td><td align="center">❌</td></tr><tr><td>Parameterized Queries</td><td align="center">❌</td></tr><tr><td>Table Calculations (Frontend)</td><td align="center">❌</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality where lineage coverage depends on SQL availability and the extent to which the LookML or calculated field is represented in the extracted SQL.
{% endhint %}

## Column Creation Support

This section outlines lineage support for columns created through direct references, aliases, aggregations, CASE statements, window functions, expressions, and LookML SQL-based dimensions.

### Column Creation from Lineage

<table data-search="false"><thead><tr><th>Transformation Type</th><th align="center">Supported</th></tr></thead><tbody><tr><td>Direct Column References</td><td align="center">✅</td></tr><tr><td>Column Aliases</td><td align="center">✅</td></tr><tr><td>Aggregations</td><td align="center">✅</td></tr><tr><td>CASE Statements</td><td align="center">✅</td></tr><tr><td>Window Functions</td><td align="center">✅</td></tr><tr><td>Expressions (Arithmetic / String)</td><td align="center">✅</td></tr><tr><td>Dot Notation Handling</td><td align="center">✅</td></tr><tr><td>Table Calculations (Frontend)</td><td align="center">❌</td></tr><tr><td>LookML Custom Dimensions (SQL-based)</td><td align="center">⚠️</td></tr></tbody></table>

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

{% hint style="info" %}
Column-level lineage is supported for SQL-based transformations that can be resolved from the available SQL definitions. Frontend-only Table Calculations are not included in SQL lineage.
{% endhint %}

## Supported Use Cases

The Looker connector supports lineage extraction across SQL-based Looks, Dashboards, Dashboard Tiles, and crawled database objects.

### Supported Lineage Scenarios

<table data-search="false"><thead><tr><th width="241">Supported Scenario</th><th>Details</th></tr></thead><tbody><tr><td>SQL-based Looks</td><td>Lineage from underlying database objects to Looks through available SQL definitions.</td></tr><tr><td>Dashboards with Multiple Tiles</td><td>Lineage across Dashboards and their associated Tiles.</td></tr><tr><td>Column-level Lineage from SQL</td><td>Column-level lineage from source database columns through SQL-based Looker content.</td></tr><tr><td>Reports Using Crawled DB Objects</td><td>Lineage for reports that reference database tables and columns available in the crawled catalog.</td></tr><tr><td>Multi-dialect Environments</td><td>SQL lineage across supported database dialects when the corresponding SQL dialect configuration is available.</td></tr><tr><td>Static SQL Query Lineage</td><td>Lineage from source tables and columns through statically available SQL queries.</td></tr><tr><td>Derived Table Lineage</td><td>Lineage involving derived tables represented in the available SQL definitions.</td></tr><tr><td>Merge Query Lineage</td><td>Lineage across Merge Queries where source attribution can be resolved from the available SQL.</td></tr><tr><td>Window Function Lineage</td><td>Column-level lineage for supported SQL transformations that use window functions.</td></tr><tr><td>SQL-based Calculated Field Lineage</td><td>Lineage for calculated fields when the calculation is represented in the available SQL.</td></tr></tbody></table>

{% hint style="info" %}
Lineage extraction depends on accessible SQL definitions, crawled database metadata, supported SQL dialect configuration, and the ability to resolve source tables and columns from the SQL.
{% endhint %}

## Partial or Limited Coverage

Certain Looker scenarios provide partial lineage coverage because the required SQL may not be available, LookML definitions may not be fully parsed, or source attribution may become complex across multiple query components.

### Scenarios

<table><thead><tr><th width="183">Scenario</th><th width="327">Limitation Description</th><th width="375">Recommendation / Workaround</th></tr></thead><tbody><tr><td>LookML-based Reports Without SQL</td><td>LookML-based reports require SQL extraction, and LookML definitions are not fully parsed for lineage.</td><td>Ensure SQL definitions are available for the affected reports and validate LookML-specific dependencies manually where required.</td></tr><tr><td>Calculated Fields</td><td>Calculated fields are supported only when the calculation is represented in the available SQL.</td><td>Validate calculated-field dependencies separately when the calculation is not represented in SQL.</td></tr><tr><td>Derived / Temporary Tables</td><td>Derived or temporary tables may appear as generic objects when the corresponding objects are not available in the catalog.</td><td>Ensure relevant source metadata is crawled and validate derived or temporary table dependencies where required.</td></tr><tr><td>Merge Queries</td><td>Complex attribution across multiple sources may limit complete lineage resolution.</td><td>Validate source attribution manually for complex Merge Queries.</td></tr><tr><td>LookML Custom Dimensions</td><td>SQL-based custom dimensions provide partial lineage coverage when the required SQL is available.</td><td>Ensure SQL definitions are available and validate complex LookML dimensions manually.</td></tr></tbody></table>

{% hint style="warning" %}
LookML-based content without accessible SQL, calculated fields that are not represented in SQL, uncataloged derived or temporary tables, and complex Merge Queries may reduce lineage completeness and column-level accuracy.
{% endhint %}

## Unsupported Scenarios

The connector does not support lineage extraction for runtime-generated SQL, unresolved query parameters, or frontend-only calculations that do not form part of the SQL lineage.

### Unsupported Lineage

<table><thead><tr><th width="202">Not Supported</th><th width="330">Description</th><th width="303">Recommendation / Workaround</th></tr></thead><tbody><tr><td>Dynamic SQL</td><td>Runtime-generated SQL and runtime parameter behavior are not resolved during lineage extraction.</td><td>Use stable SQL definitions where possible and validate dynamic dependencies manually.</td></tr><tr><td>Parameterized Queries</td><td>SQL placeholders and parameter values are not interpreted for lineage generation.</td><td>Validate parameter-dependent source relationships separately where required.</td></tr><tr><td>Table Calculations</td><td>Frontend-only Table Calculations are not part of SQL lineage and are not captured as source-to-target SQL relationships.</td><td>Validate frontend calculation dependencies separately where required.</td></tr><tr><td>Frontend-only Calculations</td><td>Calculations that do not appear in the extracted SQL are not available for SQL-based lineage generation.</td><td>Ensure applicable calculations are represented in SQL where lineage coverage is required.</td></tr></tbody></table>

{% hint style="info" %}
Unsupported scenarios do not generate complete lineage and may result in missing or disconnected lineage relationships within lineage visualization.
{% endhint %}

## Current Functional Status

This section outlines the current lineage capabilities and coverage of the Looker connector.

<table data-search="false"><thead><tr><th width="212">Status Area</th><th width="556">Details</th></tr></thead><tbody><tr><td>Overall Coverage</td><td>Production-ready coverage across SQL-based Looks, Dashboards, Dashboard Tiles, static SQL queries, derived tables, and supported database sources.</td></tr><tr><td>Lineage Depth</td><td>Table-level and column-level lineage from underlying database objects through SQL-based Looker content.</td></tr><tr><td>Supported Inputs</td><td>Looks, Dashboards, Dashboard Tiles, Merge Queries, Static SQL Queries, Derived Tables, supported SQL-based calculated fields, and crawled database objects.</td></tr><tr><td>Functional Scope</td><td>End-to-end lineage from underlying database tables and columns through SQL queries to Looker Looks and Dashboards.</td></tr><tr><td>Transformation Support</td><td>Direct column references, aliases, aggregations, CASE statements, window functions, arithmetic and string expressions, and dot notation handling are supported.</td></tr><tr><td>Limitation Areas</td><td>LookML-based reports, LookML custom dimensions, SQL-based calculated fields, derived or temporary tables, and complex Merge Queries have partial coverage.</td></tr><tr><td>Unsupported Areas</td><td>Dynamic SQL, parameterized queries, and frontend-only Table Calculations are not supported for lineage extraction.</td></tr><tr><td>Resulting Output</td><td>Robust lineage for structured SQL-based Looker environments, including column-level tracking, with partial coverage for LookML-based constructs and unsupported coverage for dynamic and parameterized query scenarios.</td></tr></tbody></table>

{% hint style="warning" %}
The Looker connector provides production-ready lineage coverage for SQL-based Looks and Dashboards, including column-level lineage across supported database sources. Direct column references, aliases, aggregations, CASE statements, window functions, expressions, and dot notation are supported. LookML-based constructs, SQL-based calculated fields, derived or temporary tables, and complex Merge Queries have partial coverage, while dynamic SQL, parameterized queries, and frontend-only Table Calculations are not supported. Manual validation may be required for advanced or SQL-independent scenarios.
{% 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/reporting-tool/looker/looker-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.