Add inititalization script & release 0.5.0 #15
Merged
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.
What does this PR implement/fix?
Add support for initialization scripts. By default harlequin-databricks will attempt to run an initialization script of SQL commands against Databricks from
~/.databricksrc
or from the file specified via the--init-path
CLI option. This means you can e.g. set a default catalog (USE CATALOG ...
), timezone, or set of user-defined variables for the session. It is possible to disable initialization via the--no-init
CLI flag, having no~/.databricksrc
file, or feedinga non-existent file path to
--init-path
.Fixes Issue
#14
Other comments?
Implementation follows that of the DuckDB and SQLite adapters. It does not implement running dot commands, as I don't think such a thing exists for Databricks.