-
Notifications
You must be signed in to change notification settings - Fork 11
Fir 8531 allow passing engine name rathe #27
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
Fir 8531 allow passing engine name rathe #27
Conversation
eg-firebolt
left a comment
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.
LGTM, left a handful of minor comments/nits
nice test coverage
| else: | ||
| engine_url = endpoint | ||
|
|
||
| assert engine_url is not None |
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.
ditto
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.
This is just for mypy check, should never really fail.
I'll think of a another way
Implemented connect function, which takes a list of connection parameters and returns database connection.
Allowed to pass engine_name rather than engine_url to connect function.
Engine url is resolved using resource manager
Added unit and integration tests
Updated examples.ipynb