You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
SQL
Use trino dialect:
INSERT INTO xxx SELECT*FROM yyy;
As of sqlfluff 2.3.2, sqlfluff trino dialect doesn't support this yet. So it causes the following exception:
RuntimeError: Grammar refers to the 'Overwrite' keyword which was not found in the trino dialect.
The syntax in the query is not (yet?) supported. Try to narrow down your query to a minimal, reproducible case and raise an issue on GitHub.
Or, even better, see this guide on how to help contribute keyword and/or dialect updates:
https://github.com/sqlfluff/sqlfluff/wiki/Contributing-Dialect-Changes#keywords
To Reproduce
The web server returns 500 to frontend, and due to this is not in JSON format, frontend fails to parse it. It only shows:
Unexpected token 'A', "A server e"... is not valid JSON
Please check your SQL code for potential syntax error in Script View.
Expected behavior
Frontend to show the exact same error message as in backend.
Python version (available via python --version)
3.8.17
SQLLineage version (available via sqllineage --version):
1.4.7
The text was updated successfully, but these errors were encountered:
reata
changed the title
Server Error 500 Not Giving Meaningful Error Message to Frontend
SqlFluff RuntimeError Triggers Server Error 500 in Frontend
Oct 16, 2023
Describe the bug
SQL
Use trino dialect:
As of sqlfluff 2.3.2, sqlfluff trino dialect doesn't support this yet. So it causes the following exception:
To Reproduce
The web server returns 500 to frontend, and due to this is not in JSON format, frontend fails to parse it. It only shows:
Expected behavior
Frontend to show the exact same error message as in backend.
Python version (available via
python --version
)SQLLineage version (available via
sqllineage --version
):The text was updated successfully, but these errors were encountered: