Open kkozhakin opened 1 month ago
We have issue handling lateral subqueries. It also throws the same exception for simple case like:
SELECT * FROM foo, LATERAL (SELECT * FROM bar WHERE bar.id = foo.bar_id) ss;
With #615 merged, the exception is gone. The current output from master branch is:
<default>.result_table.f1 <- <default>.tmp_base.f1
<default>.result_table.f2 <- <default>.tmp_base.f2
<default>.result_table.f3 <- <default>.b.f1
<default>.result_table.f4 <- <default>.b.f2
<default>.result_table.f5 <- <default>.b.f3
schema_1.table_1.* <- <default>.result_table.*
Parsing column lineage from lateral subquery is another story then. <default>.b.f1
<default>.b.f2
and <default>.b.f3
here are less desirable but requires further effort.
Among the three, <default>.b.f1
comes from constant values, we have #480 to track that.
Describe the bug LATERAL with VALUES doesn't work
SQL Paste the SQL text here. For example:
To Reproduce Note here we refer to SQL provided in prior step as stored in a file named
test.sql
Expected behavior A clear and concise description of what you expected to happen, and the output in accordance with the
To Reproduce
section.Python version (available via
python --version
)SQLLineage version (available via
sqllineage --version
):