MySQL - Lineage
This article outlines the lineage coverage, configuration settings, metadata handling, supported scenarios, component behaviors, process flow, and known gaps for lineage extraction in MySQL. The lineage process analyzes SQL statements from datasets, views, and query logs to generate table-level and column-level lineage. It helps improve data visibility and impact analysis by tracking data movement across tables, views, and SQL-based transformations within MySQL environments.
Lineage Configuration Requirements
Accurate lineage extraction depends on specific configuration settings and metadata availability. These requirements must be properly configured and available to ensure successful lineage generation and source-target resolution.
Configuration Requirements Table
MySQL Connection
MySQL connection must be configured and successfully crawled
Dataset SQL
Datasets must contain valid SQL statements
Schema Metadata Availability
Required schemas and tables must be available in metadata
Query Log Ingestion
Query log ingestion can be enabled to support runtime lineage extraction
Lineage Processing Limits
Recommended lineage processing limit settings should be configured
Query Cleanup
Query cleanup is recommended to improve SQL parsing success
Missing metadata, invalid SQL statements, or unavailable schema information may prevent lineage generation or result in incomplete lineage paths.
Lineage Components
Tables
✅
Views
✅
Columns
✅
SQL Queries (Static SQL)
✅
Query Logs
⚠️
Stored Procedures / Functions
⚠️
Triggers
⚠️
Temporary Objects
⚠️
Cross-Schema References
⚠️
Dynamic SQL
❌
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
Column Creation Support
This section outlines lineage support for column creation and transformation scenarios.
Column Creation from Lineage
Direct Column Mapping
✅
Alias Mapping
✅
Expressions
⚠️
Aggregations
⚠️
Derived Columns
⚠️
Temporary Columns
⚠️
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
Supported Use Cases
The connector supports lineage extraction across standard MySQL SQL workloads and metadata-driven transformations. These use cases represent scenarios where lineage extraction functions as expected.
Supported Lineage Scenarios
View to Source Table Lineage
Lineage extraction from views to the underlying source tables
Table to Table Lineage
Tracking lineage between source and target tables
Direct Column Mapping
Source-to-target column mapping for direct assignments
Alias Mapping
Lineage for renamed columns and aliases
Simple Expression Lineage
Column lineage for basic SQL expressions
Cross-Schema Lineage
Lineage across schemas within the same MySQL instance
Static SQL-Based Transformations
Lineage generated from static SQL-based ELT processes
Query Log Lineage
Lineage extraction from supported query log information
Lineage extraction is based on SQL statements available in datasets, views, and supported query log sources.
Partial or Limited Coverage
Certain scenarios provide only partial lineage coverage due to SQL complexity, metadata limitations, or processing constraints.
Scenarios
Stored Procedures and Functions
Coverage is limited to static SQL portions that can be analyzed
Triggers
Only supported where static SQL logic can be extracted
Complex SQL Queries
Nested queries, multiple CTEs, and complex query structures may not be fully resolved
UNION Operations
Lineage generation may be incomplete for UNION-based queries
Aggregations
Partial column-level lineage for aggregation functions
Derived Columns
Complex derivation logic may not be fully represented
Temporary Tables and Objects
Temporary object lineage may be incomplete
Cross-Connection or Federated Queries
Limited support for lineage across external or federated sources
Non-ASCII Queries
SQL parsing may be limited for non-ASCII query content
Complex SQL patterns and temporary processing structures may result in incomplete column-level lineage even when lineage extraction succeeds.
Unsupported Scenarios
The connector does not support lineage extraction for certain SQL execution patterns and procedural logic due to limitations in metadata availability and query resolution.
Unsupported Lineage
Dynamic SQL
Runtime-generated SQL statements
Procedural Logic
Complex logic involving loops, conditions, and cursors
Application-Level Embedded SQL
SQL executed within applications that are not captured as datasets or query logs
Runtime Query Generation
Queries constructed dynamically during execution
Non-Captured External Processing
Transformations performed outside available metadata and query sources
Unsupported scenarios will not generate lineage and may appear disconnected or absent in lineage visualization.
Current Functional Status
This section outlines the present state of lineage coverage supported by the MySQL connector based on the available capabilities and limitations.
Overall Coverage
Partial coverage across MySQL SQL workloads
Lineage Depth
Reliable table-level lineage with basic column-level lineage support
Supported Inputs
Tables, views, datasets, static SQL queries, and query logs
Functional Scope
Lineage extraction for standard SQL-based transformations and object relationships
Limitation Areas
Dynamic SQL, procedural logic, complex queries, aggregations, derived columns, and federated processing
Resulting Output
Strong table-level lineage with column-level lineage available for supported SQL patterns
Coverage remains partial because dynamic SQL, procedural logic, complex transformations, and certain query structures cannot be fully resolved. Manual validation or lineage adjustments may be required for advanced MySQL workloads.
Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA
Was this helpful?