Releases: databricks/dbt-databricks
v1.7.3
What's Changed
The big change in this release is that we fixed the issue where every single dbt action initiated a new connection to Databricks. We will now reuse a connection if there is a thread-local connection that matches the compute the user has selected.
This change will be most apparent if your dbt operations are very short lived, such as tests against a small table, as there is now less time spent in connection negotiation; for longer operations, the time spent in computing and transmitting the result set is more significant than the time spent on connecting.
If for some unforeseen reason this change negatively impacts performance:
a.) You can turn it off by setting the DBT_DATABRICKS_LONG_SESSIONS
environment variable to false.
b.) Please file an issue so we can investigate.
Fixes
- Allow session re-use by @rcypher-databricks in #517
- Fixing list_schemas so that we stop trying to create schemas that exist by @benc-db in #529
Under the Hood
- Refactor macro tests so that we can move macros by @benc-db in #524
- Updating Python Functional Tests by @benc-db in #526
- Refactoring to align with dbt-core organization: Part I by @benc-db in #525
Full Changelog: v1.7.2...v1.7.3
1.7.2
The big news is that the ability to choose separate compute by model is now available. Until I get updated docs out, please look here for usage notes: #333 (comment)
What's Changed
- Updates to warehouse-per-model logging and tests by @rcypher-databricks in #511
- Persist docs on incremental only if changed by @benc-db in #513
- Enable access control for job runs by @benc-db (thanks @srggrs!) in #518
- View column comments can now be persisted, hive docs generate now works by @benc-db in #519
Full Changelog: v1.7.2b2...v1.7.2
1.5.7
Fixes
This release is to declare that the 1.5.x branch is not compatible with databricks-sql-connector version 3.0.0
Full Changelog: v1.5.6...v1.5.7
1.7.2b2
This is a beta release for testing the ability to specify compute on a per model basis. For full instructions on how to use this capability, for now see #333, where I will include the provisional instructions. DO NOT RELY ON THIS CAPABILITY FOR PRODUCTION WORKLOADS YET. We are looking for users to try out this feature and report any bugs they encounter.
Full Changelog: v1.7.1...v1.7.2b2
1.7.1
Under the Hood
- Revert to client-side filtering for large projects in an attempt improve performance of doc generation by @benc-db (thanks @mikealfare for the help) (503)
Full Changelog: v1.7.0...v1.7.1
1.7.0
What's Changed
This release is mostly about performance and compatibility with 1.7.x of dbt-core. Expect more to come in the coming weeks for expanding config, and config change management, for Materialized Views and Streaming Tables.
Features
- Implementing metadata freshness checks by @benc-db in #481
- Catalog fetch improvement by @benc-db in #486
- Faster dbt seeds by @benc-db (thanks @nrichards17 for the original PR!) in #498
Under the Hood
- Add node_info to SQLQuery events by @davidharting (thanks!) in #494
- 1.7.1 Compat by @benc-db (with help from @mikealfare!) in #499
New Contributors
- @davidharting made their first contribution in #494
Full Changelog: v1.7.0rc1...v1.7.0
1.6.7
v1.7.0 RC1
What's Changed
- Getting compatibility with 1.7.0 RC by @benc-db in #479
- As part of the above change, fixed a bug with constraints where if a column had a primary key constraint and a not null constraint (a pre-req for primary key), it could fail depending on the order the constraints were run in.
- As part of the above, included support for specifying foreign key constraints using the dbt constraint expression syntax. Currently this support is restricted to single column foreign keys.
Full Changelog: v1.6.6...v1.7.0rc1
v1.6.6
1.5.6
What's Changed
Includes the following:
- Updated the Databricks SDK dependency so as to prevent reliance on an insecure version of requests (460)
- Update logic around submitting python jobs so that if the cluster is already starting, just wait for it to start rather than failing (461)
- Add
fetchmany
, resolves #408 (Thanks @NodeJSmith) (#409) - Relaxed the constraint on databricks-sql-connector to allow newer versions (#436)
- Follow up: re-implement fix for issue where the show tables extended command is limited to 2048 characters. (#326). Set
DBT_DESCRIBE_TABLE_2048_CHAR_BYPASS
totrue
to enable this behaviour.
Full Changelog: v1.5.5...v1.5.6