Using JOIN with ON/USING keyword fails to determine source tables when followed by a parenthesis
See original GitHub issueI have the following queries:
create table target_table as (
select *
from source_table_a
join source_table_b
on (source_table_a.some_id = source_table_b.some_id))
)
create table target_table as (
select *
from source_table_a
join source_table_b
using (some_id)
)
This causes the table lineage to not extract source_table_a
and source_table_b
as sources. However, when the parenthesis are removed around source_table_a.some_id = source_table_b.some_id)
and some_id
it works properly.
Any help or insight would be greatly appreciated! 😀
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Why are parenthesis in my WHERE clause messing up the ...
When I try to use parenthesis in a WHERE statement within a UNION, and then JOIN it with another table, it gives me...
Read more >ORA-00907: missing right parenthesis Solution - Database Star
ORA-00907 Cause. When working with Oracle SQL, all left parenthesis (the “(” character) must be paired with a right parenthesis character ...
Read more >Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
Read more >Common SQL syntax errors and how to resolve them
In this article, we are going to describe some of the most common SQL syntax errors, and explains how you can resolve these...
Read more >How to solve the query failure when selecting a table with ...
When using SQL Server as the data source during data import, if the selected table contains brackets ([ or ]) in the table...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let’s release v1.3.5 within next two days.
Sorry for jumping in @reata, but do you have any plan to release this fix to PyPI? I hit the same issue with 1.3.4 and it’d be great if I could have the fixed version wheel via PyPI.