Sqllineage

Latest version: v1.5.2

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

Scan your dependencies

Page 1 of 7

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

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

1.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)

1.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)

1.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)

1.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)

Page 1 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.