feat: allow username/password in connection string #27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scottlepp
requested review from
arikfr,
susodapop,
moderakh and
yunbodeng-db
as code owners
scottlepp
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently using the Databricks ODBC driver, but would like to test this driver out as an alternative. Can't create tokens in Databricks community edition so can't test it. This change allows setting username/password on the connection string, similar to what the ODBC driver allows.
This is just for testing purposes, though also allows those evaluating Databricks to connect to community edition with this driver.
example DSN:
databricks://scott:password@community.cloud.databricks.com/sql/protocolv1...