Closed piekill closed 1 month ago
Thanks for reporting this issue. I don't think we carefully designed for frontend visualization back when developing metadata providers.
As you mentioned, we do need a more clever way to let the web server "remember" the metadata provider instead of hard code it in /lineage controller.
Describe the bug When I provide the metadata, the printed column level lineage is correct, but the figure generated doesn't contain this information. Printed column lineage:
<default>.res.c1 <- db1.tab1.c1
SQL
To Reproduce
Expected behavior If I use the following sql (replace c1 with a.c1):
I can get the expected figure (the printed column lineage is the same):
Python version (available via
python --version
)SQLLineage version (available via
sqllineage --version
):Updated I think the reason is that metadata provider is not currently used in visualization:
https://github.com/reata/sqllineage/blob/5b7173ee6130c907294c5e51a12e6ecf4d12025a/sqllineage/drawing.py#L168
I can get the expected behavior if I manually set the metadata_provider here. I guess there could be a better way of doing this.