[BUGFIX] 0.18.4 - Fix Snowflake error when using alternative connection details format. #9056
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Copy of the V1 fix so that we can release as part of
0.18.4
Changes the behavior of
SnowflakeDatasource.get_execution_engine()
so that it no longer re-creates thesqlalchemy.engine.Engine
object and instead re-uses the one used by the Datasource for.test_connection()
.This solves 2 problems...
sqlalchemy.engine.Engine
objects at runtime.sqlalchemy.engine.Engine
objects.This is a more minimal version of the following bugfix. Issues with SQLite are forcing the more minimal PR (9055).
Other notes
For Snowflake this also means that when using the
authenticator=externalbrowser
query param, the browser will only need to auth once instead of 2wice for every connection.