Releases: reata/sqllineage
v1.5.6
This is a bugfix release with a couple of dialect-specific minor enhancements:
Enhancement
Bugfix
v1.5.5
This is a tech refresh release, including the following changes:
- unpin sqlparse and sqlfluff dependencies to allow more flexible dependency resolution when using sqllineage as a library. Enable nightly CI to test against compatibility on latest version of sqlparse and sqlfluff
- leverage Python 3.9 new syntax features to simplify code base, including: 1) use built-in type hinting generic in standard collections (list, dict, tuple, etc.); 2) use dictionary merge operator (|)
- use pyproject.toml as centralized configuration file for all tools (tox, black, ruff, mypy, etc.)
- use ruff as linter to replace flake8
- use hatch as build backend to replace setuptools
- sqllineagejs frontend tool chain refresh: 1) upgrade react, redux, mui to latest major version; 2) use vite as frontend build tool to replace react-scripts; 3) add eslint as linter and prettier as formatter;
Bugfix
v1.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 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
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
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
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
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)