sqllineage VS elementary

For the open source there is this library https://github.com/reata/sqllineage.

Is the idea here that it's inspired by re_data due to using dbt transformations underneath or because it's reposted looking nearly the same? (or both?)

Looks like much of the lineage code is also largely a wrapper around this library: https://github.com/reata/sqllineage

Would be curious to understand the project's purpose and unique contributions vs. the underlying dependencies powering it as there seems to be some ambiguity. Is this just a wrapper around dbt transformations and a lineage library in one package? Can I just use them directly?

Check out https://github.com/elementary-data/elementary

In this case, do https://github.com/elementary-data/elementary or https://greatexpectations.io help?

That makes explain little easier to read. No graph though. Also https://github.com/elementary-data/elementary should know howto draw pretty graphs for data lineage ( ie. what columns comes where and is used how)

there is elementary lineage / elementary-data which seems to be good try to solve those problem, i havent tested it well https://github.com/elementary-data/elementary

Some things you might be interested in are re_data and Elementary Data.

Hi all, As part of building Elementary (open source data reliability), we implemented support of a new Snowflake feature (write operations in the access_history view). The change they made is most useful for understanding data lineage, which we solve (among other use cases :)).

I recently stumbled on an open-source tool with a similar premise: https://github.com/elementary-data/elementary-lineage

you can check it out

Hi! we are working on an open source data lineage solution that might be helpful for your use case to learn the relationship between tables, we don't support column level just yet but we are working on it. Please let me know if we can help somehow and feel free to check it out here - https://github.com/elementary-data/elementary-lineage