Sqllineage

Latest version: v1.5.4

Safety actively analyzes 723217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 7

1.5.4

In this release, we deprecated Python 3.8 and added support for Python 3.13 based on Python end-of-life schedule.

The most notable enhancement is upgrading sqlfluff to 3.3.1. As a result, we can now support Impala dialect and
StarRocks dialect. Many parser issues are also fixed automatically by sqlfluff upgrade.

Enhancement
-------------
* Add Support for Python 3.13 (682) reata
* Drop Support for Python 3.8 (677) reata
* Upgrade sqlfluff dependency to 3.3.1 (644) rubytobi
* Support for Impala Dialect (645)
* support Doris or StarRocks (498)

Bugfix
-------------
* Inconsistent order of lineage tuples (652) rubytobi
* Metadata wrongly used in INSERT INTO statement column lineage (648) reata
* clickhouse <rename> not handled (642) reata
* Not read SQLfluff nested configs (628) lkurgan55
* False negative for Scalar Subquery used in Function (614) reata
* Column level lineage not drawn properly when metadata is provided (597) reata
* Tsql table names with square brackets are not resolved correctly (583) reata

1.5.3

This is a security release to upgrade some dependencies to latest version as we receive vulnerability alerts.
We strongly recommend that all sqllineage installations be upgraded to this version immediately.

This release also includes an improvement regarding metadata provider.

Enhancement
-------------
* set target table column name from MetaDataProvider (`528`) delphisharp

1.5.2

Not secure
Enhancement
-------------
* Enable support of sqlfluff context (548) reata
* Support Change Configure Default Schema At Runtime (536) delphisharp

Bugfix
-------------
* Parse column level lineage incorrect (584) maoxingda
* Metadata Masked When Table was in a previous UPDATE statement (577) reata
* Clickhouse SQL 'GLOBAL IN' not support (554) reata
* Support json_tuple in SELECT clause in Hive (483) reata

1.5.1

Not secure
This is a bugfix release mostly driven by community contributors. Thanks everyone for making SQLLineage better.

Enhancement
-------------
* Allow unambiguous column reference for JOIN with USING clause (558) kkozhakin
* Make Lateral Column Alias Reference Configurable (539) maoxingda & reata
* Add an Argument to Exclude SubQuery Column Node in Column Lineage Path (526) delphisharp

Bugfix
-------------
* Not fully processed top-level subquery in DML (564) maoxingda
* Missing target table with tsql parsing into statements with union (562) reata
* The second and subsequent case when subqueries in the select_clause are not correctly recognized (559) maoxingda
* SQLLineageConfig boolean value returns True for all non-empty strings (551) maoxingda
* Column lineage does not traverse through CTE containing uppercase letters (531) reata

1.5.0

Not secure
Great thanks to lixxvsky for contributing on MetaData-awareness lineage. Now we're able to generate more accurate
column lineage result for `select *` or select unqualified columns in case of table join through a unified
MetaDataProvider interface.

Also a breaking change is made to make ansi the default dialect in v1.5.x release as we target ultimately deprecating
non-validating dialect in v1.6.x release.

Breaking Change
---------------
* Make ansi the Default Dialect (518)

Feature
-------------
* Metadata Provider to Assist Column Lineage Analysis (477) lixxvsky & reata

Enhancement
-------------
* Add a Configuration for Default Schema (523)
* Silent Mode Option to Suppress UnsupportedStatementException (513) kkozhakin
* Support Lateral Column Alias Reference Analyzing (507) maoxingda
* Skip Lineage Analysis for SparkSQL Function Related Statement (500)
* update statement column lineage (487) maoxingda

Bugfix
-------------
* subquery mistake alias as table name in visualization (512)
* InvalidSyntaxException When SQL Statement Ends with Multiple Semicolons (502)
* Misidentify Binary Operator * As Wildcard (485)
* adding type cast operator produces different results for redshift dialect (455)

1.4.9

Not secure
This is a bugfix release where we closed a bunch of issues concerning CTE and UNION

Bugfix
-------------
* Not Using Column Name Specified in Query For CTE within Query (486)
* CTE (Common Table Expressions) within CTE (484)
* lineage inaccurate when CTE used in subquery (476)
* UNION ALL Queries resolves column lineage incorrectly (475)
* Missing table when parsing sql with UNION ALL (466)
* No target tables in UPDATE statement using CTE (453)

Page 1 of 7

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.