v1.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

v1.5.2

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

v1.5.1

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

v1.5.0

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)

v1.4.9

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)

v1.4.8

Enhancement

• Support Python 3.12 (#469)
• programmatically list supported dialects (#462)
• add versioning of package to cli (#457)
• Add Support of DROP VIEW statements (#456)
• support split SQL statements without semicolon in tsql (#384)

Bugfix

• SqlFluff RuntimeError Triggers Server Error 500 in Frontend (#467)
• ignore lineage for analyze statement (#459)

v1.4.7

Enhancement

• Support subquery in VALUES clause (#432)
• Dialect='tsql' should return warning when no semicolons are detected (#422)
• Restricting folder and files user can access from frontend (#405)
• throw exception when the statement missing the semicolon as splitter (#159)

Bugfix

• AttributeError raised using parenthesized where clause (#426)
• qualified wildcard recognized as wrong column name (#423)

v1.4.6

In this release, we finally reach the milestone to make all sqlparse only test cases passed with sqlfluff implementation.
That's a big step in ultimately deprecating sqlparse. Also by upgrading to latest version of sqlfluff (with our PR merged),
we enjoy the benefits of improved sqlfluff performance when parsing some SQLs with nested query pattern.

Enhancement

• Improve sqlfluff Performance Issue on Nested Query Pattern (#348)
• Reduce sqlparse only test cases (#347)

Bugfix

• Missing Source Table for MERGE statement when UNION involved in source subquery (#406)
• Column lineage does not work for CAST to Parameterized Data Type (#329)
• Can't handle parenthesized from clause (#278)

v1.4.5

Enhancement

• Switch to PyPI Trusted Publishers (#389)
• Support tsql Declare Statement (#357)

Bugfix

• Exception for Subquery Expression Without Source Tables (#401)
• Not Supporting Create Table AS in postgres (#400)
• Failed to handle UNION followed by CTE (#398)
• Not handling CTE inside DML query (#377)
• Failed to parse UNION inside CTE (#376)

v1.4.4

Enhancement

• BigQuery Specific MERGE statement feature support (#380)
• Support snowflake create table...clone and alter table...swap (#373)
• Parse Column Lineage When Specify Column Names in Insert/Create Statement (#212)

Bugfix

• Switching Dialect in UI only works When Explicit Clicked (#387)
• No Column Lineage Parsed for DML with SELECT query in parenthesis (#244)