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
I searched the issues and found no similar issues.
What Happened
Unable to parse any query in the Trino dialect.
I searched through existing issues, and it seems that nobody has reported the problem.
And judging by the feature requests for some Trino features support, it typcially works, i.e. the problem doesn’t affect other people and should be specific to my setup, but I can’t guess what it might be.
Expected Behaviour
sqlfluff parse some_code.sql -d trino prints the parse tree
Observed Behaviour
$ sqlfluff parse scripts/tmp/test.sql -d trino
RuntimeError: Grammar refers to the 'Transient' 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
How to reproduce
Content of test.sql might be any, in this case, say
createtableusersas (select name, email from old_users);
The error never changes regardless of the content of the file.
Search before asking
What Happened
Unable to parse any query in the Trino dialect.
I searched through existing issues, and it seems that nobody has reported the problem.
And judging by the feature requests for some Trino features support, it typcially works, i.e. the problem doesn’t affect other people and should be specific to my setup, but I can’t guess what it might be.
Expected Behaviour
sqlfluff parse some_code.sql -d trino
prints the parse treeObserved Behaviour
How to reproduce
Content of test.sql might be any, in this case, say
The error never changes regardless of the content of the file.
Dialect
Trino
Version
Configuration
Are you willing to work on and submit a PR to address the issue?
Code of Conduct
The text was updated successfully, but these errors were encountered: