-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't handle parenthesized from clause #278
Comments
Thanks for reporting it, issue acknowledged. I already fixed a lot of edge cases regarding brackets, but this seems never ending. I need to rethink how should we handle this. |
I have another example where the parser just failed completely:
If i removed the bracket
EDIT: I think with the first query, there's a space between the 2 brackets, that caused the exception |
@cuong-pham Thanks for reporting this. Yes the space is one problem, which I can make it go away easily. However, the following SQL still fails to parse out any source tables. |
adding one more example to the mix as this might be a frequent case - here i am only able to get the source and target table lineage and not the column lineage. Query I was trying out is : INSERT INTO db.schema.table1( col1 , col2 , col3) if I format the sql a bit like below by removing the brackets for the select statement i get the column lineage INSERT INTO db.schema.table1 |
@mishbahr @cuong-pham Can you let me know the SQL dialect you're using? I tried MySQL and it's valid syntax, not sure if you're using other database. @JustinJanz Please refer to #244 for your case. |
@reata I was using Athena for that query. |
@reata I was using Postgres |
Using
sqllineage==1.3.5
Given auto generated query from a third party package.
Input
Output (incorrect)
However if I remove the extra brackets from the query:
Output:
The text was updated successfully, but these errors were encountered: