-
Notifications
You must be signed in to change notification settings - Fork 270
Feat : Trino plugin Integration - Querybook #681
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
skimmed
querybook/server/lib/query_executor/executor_template/templates.py
Outdated
Show resolved
Hide resolved
querybook/server/lib/query_executor/executor_template/templates.py
Outdated
Show resolved
Hide resolved
querybook/server/lib/query_executor/executor_template/templates.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR looks good to me! Just some minor linting fix thats needed.
Besides the requirements/base.txt issue, can you also update the documentation of https://www.querybook.org/docs/setup_guide/connect_to_query_engines#overview to have Trino as Tier 2 (we can move to Tier 1 later if it works well) and change the package to trino instead of sqlalchemy-trino?
Actually, nvm about the requirements/base.txt change. Just note that it will be removed in requirements/base.txt in 3.0 |
3653de4
to
c100b3a
Compare
Integrating an official Trino Plugin for query book backed-up with native Trino-python-client.
Issue Link : #509