NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #2032 most downloaded on PyPI
The Databricks adapter plugin for dbt
Last release 3 days ago
01 Oct 2026
Ships fairly regularly
a new release about every 3 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
10 versions withdrawn
withdrawn after publishing
5 years old
186 releases · first in 2021
One column per quarter.
Nothing published for this version
Support auth_type: env-oidc and auth_type: file-oidc for authenticating via workload identity federation, with a new oidc_token_filepath profile confi
auth_type: env-oidc and auth_type: file-oidc for authenticating via workload identity federation, with a new oidc_token_filepath profile config for the latter (thanks @Gerrit-K!) (#1666)SHOW GRANTS result columns case-insensitively so grant reconciliation does not crash when connectors return lowercase names (thanks @TangoEnSkai!) (#1650 resolves #782)ALTER for an ordinary view only when the existing relation is also an ordinary view by @sd-db in #1687databricks_tags to materialized views and streaming tables while preserving tags across replacements by @sd-db in #1686dbt-core upper bound to <1.12.6 to include dbt-core 1.12.4 and 1.12.5 by @sd-db in #1689databricks_tags keys in ALTER … SET TAGS by @sd-db in #1667databricks_tags keys in ALTER COLUMN … SET TAGS, without unsetting remote-only tags by @sd-db in #1668Full Changelog: v1.12.5...v1.12.6
Replace an existing table or view with a metric view using backup-and-create instead of CREATE OR REPLACE VIEW ... WITH METRICS by @sd-db in #1640 (re
CREATE OR REPLACE VIEW ... WITH METRICS by @sd-db in #1640 (resolves #1639)databricks.sql log records when mirroring them into dbt logs by @sd-db in #1642 (resolves #1637)Full Changelog: v1.12.4...v1.12.5
CREATE OR REPLACE VIEW ... WITH METRICS (#1640 resolves #1639)databricks.sql log records when mirroring them into dbt logs (#1642 resolves #1637)dbt-core upper bound to <1.12.4 to include dbt-core 1.12.3 (#1656)Bump databricks-sql-connector ceiling to <4.4.1 and pin to 4.4.0, which requires thrift>=0.24.0 ; resolves CVE-2026-48586 (data amplification DoS), CV…
credential and encryption clauses in logged SQL, regardless of keyword case (thanks @SreeramaYeshwanthGowd!) (#1610 resolves #1609)delete+insert with a composite unique_key from deleting unmatched rows on DBR below 17.1 (thanks @SreeramaYeshwanthGowd!) (#1612 resolves #1611)pytest-rerunfailures lower bound to >=16.2 and remove the SchemaNameVarMixin workaround so min-deps CI no longer pins 14.0, which leaked class-scoped dbt test fixtures across reruns (test-only, no runtime impact) by @sd-db in #1618databricks-sql-connector ceiling to <4.4.1 and pin to 4.4.0, which requires thrift>=0.24.0; resolves CVE-2026-48586 (data amplification DoS), CVE-2026-41603 (TLS cert hostname bypass), and CVE-2026-43868 (memory allocation) by @mitchelllisle in #1623 (resolves #1622)docs/ into docs/flow/ and docs/guides/, and sync materialization flow diagrams with the current macros by @sd-db in #1627dbt-common upper bound to <1.39.0 (thanks @itsnamangoyal!) (#1630)Full Changelog: v1.12.3...v1.12.4
dbt-databricks 1.12.3 (Jul 29, 2026)
catalog_database in v2 catalogs.yml to route Unity catalog models to a physical catalog independent of the dbt catalog name (requires dbt-core>=1.12 and dbt-adapters>=1.24.4). (thanks @aahel!) (#1590)databricks_tags as configuration changes by diffing against existing table tags. by @sd-db in #1602 (resolves #1601)--full-refresh is provided alongside view_update_via_alter: true and use_materialization_v2: true (thanks @aarushisingh04!) (#1456 resolves #1404)dbt clone and rebuilds over an existing shallow clone by @saishreeeee in #1592 (resolves #1165, follow-up by @sd-db in #1608)MANAGED_TABLE_FORMAT by emitting .format("iceberg") instead of the parquet sentinel from resolve_file_format (thanks @Divya-Kovvuru-0802!) (#1593 resolves #1591)keyring dependency and its transitive packages by @sd-db in #1588dbt-core upper bound to <1.12.1 to include dbt-core 1.12.0 by @sd-db in #1605Full Changelog: v1.12.2...v1.12.3
dbt-databricks 1.12.2 (Jul 9, 2026)
use_catalogs_v2: true in dbt-core) (#1440)skip_optimize model config to opt out of the post-materialization OPTIMIZE call without dropping zorder / liquid_clustered_by / auto_liquid_cluster from the table definition. Useful when OPTIMIZE is delegated to Predictive Optimization or scheduled out of band. Complements the existing run-wide DATABRICKS_SKIP_OPTIMIZE var by allowing project-, folder-, or model-level opt-out via standard dbt config inheritance (#703).connection_parameters: {use_kernel: true} for SQL warehouses, with personal access token or Databricks OAuth (M2M/U2M) auth (requires databricks-sql-connector[kernel] on Python 3.10+; Azure service principals are not supported by the kernel) (#1576)contract.enforced is false (#1557)skip_not_matched_step merge config in the adapter config schema. It was previously declared with a typo (skip_non_matched_step); the merge macro already read the correct key, so merge behavior is unchanged (#1562).expression field on primary_key constraints on the V1 materialization path. A primary key declared with expression: RELY (or any trailing clause) previously had its expression silently dropped. (#1551)databricks_tags for incremental models on the V1 materialization path (#1520 closes #1307)DbtRuntimeError when a Python model job run terminates with a non-success result_state (e.g. FAILED/TIMEDOUT) instead of returning silently (#1477)expression (e.g. RELY) being dropped and re-added on every incremental run. Regression: changing the expression on an existing PK/FK (RELY↔NORELY, or an expression-form FK's target) is no longer applied on incremental runs — use --full-refresh. (#1552 closes #1513)incremental_apply_config_changes in the V1 incremental merge path, allowing users to skip metadata diff queries (tags, column_tags, constraints, column_masks, tblproperties, describe_extended) when set to false. Matches the existing V2 behavior. (#1467 partially resolves #1402)databricks_tags on Unity Catalog views updated via ALTER (view_update_via_alter: true) (#1526 closes #1525)tblproperties to metric_view models at create time, not only on a later alter/replace run (#1530 closes #1527)INSERT ... BY NAME in the replace_where/microbatch strategies on DBR 18.0+ (and SQL warehouses), since older clusters reject the BY NAME ... REPLACE WHERE combination with a parse error (#1539 resolves #1532)tblproperties were read as configuration drift; the diff now compares only the configured properties (#1350 closes #1314).view_update_via_alter from re-issuing a redundant ALTER VIEW ... AS on every run (#1546)view_update_via_alter issues ALTER VIEW AS; reapply persisted column comments after the query update (#1357)databricks-sql-connector upper bound to <4.3.1 to support 4.3.0 (#1518)dbt-adapters upper bound to <1.25.0 (#1507)databricks-sdk upper bound to <0.118.0 to pick up 0.117.0, which fixes WorkspaceClient construction failing with CONTEXT_UNAVAILABLE_FOR_REMOTE_CLIENT on Spark Connect clusters (#1517 closes #1252)dbt-core upper bound to <1.11.13 to include dbt-core 1.11.12 (#1578)add_query, get_relation_config, is_uniform, has_dbr_capability, and is_cluster for dbt's record/replay framework (test-only, no runtime impact) (#1508)Kernel Integration Tests workflow that runs the functional suite against the SQL-warehouse profile through the connector's Rust kernel backend (DBT_DATABRICKS_USE_KERNEL=1) (test-only, no runtime impact) (#1576).copy_into, clone, seeds, SQL UDFs, split_part, sync_all_columns type widening, catalog table_format, and Python models — shifting assertions to server-observable state rather than compiled SQL or log output; add unit coverage for the live event/logging classes; make stateful functional tests rerun-safe; and add CI upkeep (a weekly Python-model notebook-folder purge and a longer unit-test timeout) (test-only, no runtime impact). (#1511, #1512, #1514, #1521, #1522, #1523, #1524, #1528, #1529, #1531, #1533, #1534, #1535, #1536, #1537, #1538, #1541, #1542, #1543, #1544, #1545, #1548, #1550, #1553, #1558, #1559, #1564, #1565, #1566, #1568, #1569, #1570, #1571, #1573, #1579, #1580, #1581, #1582)Full Changelog: v1.12.1...v1.12.2
Expose job_id, job_run_id, and task_run_id from the Databricks Jobs dbt_task runtime in adapter_response, enabling correlation between dbt runs and Da
job_id, job_run_id, and task_run_id from the Databricks Jobs dbt_task runtime in adapter_response, enabling correlation between dbt runs and Databricks workflow executions via run_results.json by @sd-db in #1451, closes #722?o=<workspace-id> in http_path route correctly for both data-plane (SQL) and control-plane (REST/Jobs/Workspace API) traffic. Requires databricks-sql-connector >= 4.2.6 and databricks-sdk >= 0.76.0. by @sd-db in #1479delta.parquet.compression.codec tblproperty when diffing relation configs, so streaming tables and materialized views are not flagged as changed after the backend started stamping it automatically by @sd-db in #1489JobRunsApi.submit debug log by @Dev-X25874 in #1471has_dbr_capability now returns True on warehouse profiles for capabilities flagged sql_warehouse_supported, so macros select the modern branch during compilation instead of the legacy fallback. by @sd-db in #1449, closes #1331databricks_tags on columns by @themattmorris in #1442, closes #1441DESCRIBE TABLE EXTENDED ... AS JSON for foreign/federated tables in get_columns_in_relation, avoiding repeated failures and extra latency on those sources by @willweld in #1472EXTRACT_CLUSTER_ID_FROM_HTTP_PATH_REGEX now stops the capture at ? / &, so any trailing query string on http_path no longer corrupts the extracted cluster id. Latent issue on legacy hosts; the fix unblocks SPOG cluster paths. by @sd-db in #1479contract.enforced to match the existing model-level gate, ensuring column-level NOT NULL / PK / FK / CHECK constraints are only applied when contract.enforced: true under use_materialization_v2: true by @sd-db in #1470, closes #1381partition_by silently losing their clustering after the first incremental run. Managed Iceberg stores partition_by as liquid clustering server-side, so the reconciler now treats partition_by as the desired clustering and no longer issues a spurious ALTER TABLE ... CLUSTER BY NONE by @sd-db in #1496, closes #1495Config construction to connection-open time so offline paths (dbt parse/list/compile) don't trigger the host-metadata probe introduced in databricks-sdk>=0.103; as a side effect, auth errors now surface at first connection rather than during profile parsing. by @sd-db in #1474databricks-sdk (now <0.105.0) and databricks-sql-connector[pyarrow] (now <4.3.0) to admit newer releases; floors unchanged. by @sd-db in #1474use_materialization_v2: true without contract.enforced: true must now set contract.enforced: true explicitly on the model. by @sd-db in #1470<1.11.12 to include dbt-core 1.11.9, 1.11.10, and 1.11.11 by @sd-db in #1505Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.12.0...v1.12.1
job_id, job_run_id, and task_run_id from the Databricks Jobs dbt_task runtime in adapter_response, enabling correlation between dbt runs and Databricks workflow executions via run_results.json (#1451 closes #722)?o=<workspace-id> in http_path route correctly for both data-plane (SQL) and control-plane (REST/Jobs/Workspace API) traffic. Requires databricks-sql-connector >= 4.2.6 and databricks-sdk >= 0.76.0. (#1479)delta.parquet.compression.codec tblproperty when diffing relation configs, so streaming tables and materialized views are not flagged as changed after the backend started stamping it automatically (#1489)JobRunsApi.submit debug log (#1471)has_dbr_capability now returns True on warehouse profiles for capabilities flagged sql_warehouse_supported, so macros select the modern branch during compilation instead of the legacy fallback. (#1449 closes #1331)databricks_tags on columns (#1442 closes #1441)DESCRIBE TABLE EXTENDED ... AS JSON for foreign/federated tables in get_columns_in_relation, avoiding repeated failures and extra latency on those sources (#1472)EXTRACT_CLUSTER_ID_FROM_HTTP_PATH_REGEX now stops the capture at ? / &, so any trailing query string on http_path no longer corrupts the extracted cluster id. Latent issue on legacy hosts; the fix unblocks SPOG cluster paths.contract.enforced to match the existing model-level gate, ensuring column-level NOT NULL / PK / FK / CHECK constraints are only applied when contract.enforced: true under use_materialization_v2: true (#1470 closes #1381)partition_by silently losing their clustering after the first incremental run. Managed Iceberg stores partition_by as liquid clustering server-side, so the reconciler now treats partition_by as the desired clustering and no longer issues a spurious ALTER TABLE ... CLUSTER BY NONE (#1496 closes #1495)pytest --reruns retry no longer inherits mutated state (rewritten schema.yml, half-built relations) from the failed attempt (test-only, no runtime impact). (#1503)pytest --reruns retry no longer inherits mutated state (updated schema.yml, leftover column tags, a running streaming-table query) from the failed attempt (test-only, no runtime impact). (#1499)dbt-tests-adapter test-dependency floor to >=1.20.0 to pick up its persist_docs fixture typo fix (test-only, no runtime impact) (#1490)Config construction to connection-open time so offline paths (dbt parse/list/compile) don't trigger the host-metadata probe introduced in databricks-sdk>=0.103; as a side effect, auth errors now surface at first connection rather than during profile parsing. (#1474)databricks-sdk (now <0.105.0) and databricks-sql-connector[pyarrow] (now <4.3.0) to admit newer releases; floors unchanged. (#1474)databricks-sql-connector ceiling to patch level (<4.3.0 → <4.2.7) so patch upgrades require an intentional bump; the locked version stays at 4.2.6. (#1497, #1498)TestChangingSchema* Python-model functional tests under min-deps (dbt-core 1.11.2), where a sibling class's source schema.yml could leak into their parse and fail with EnvVarMissingError. (#1488)use_materialization_v2: true without contract.enforced: true must now set contract.enforced: true explicitly on the model.<1.11.12 to include dbt-core 1.11.9, 1.11.10, and 1.11.11 (#1505)Add support for metric views as a materialization by @benc-db in #1285
databricks_tags for table and column tagging. This can now be configured by setting tag values to empty strings "" or None. by @canbekley in #1339DESCRIBE TABLE EXTENDED ... AS JSON call, replacing multiple information_schema queries. Falls back to information_schema on older runtimes. Gated behind use_describe_as_json_for_relation_metadata behavior flag, off by default. by @tejassp-db in #1432SCHEDULE EVERY and TRIGGER ON UPDATE refresh modes for materialized views and streaming tables, with parser and diff coverage so relations whose actual refresh is not CRON no longer crash on subsequent runs by @sd-db in #1434, closes #1293metric_view failing with METRIC_VIEW_INVALID_VIEW_DEFINITION when models use bare {{ ref(...) }} for the source: field by @sd-db in #1430, closes #1361RefreshConfig.__eq__ self/other typo where two configs with the same cron but different time_zone_value compared equal by @sd-db in #1434refresh.py so the adapter imports on environments shipping pydantic v1 by @sd-db in #1461databricks_tags defined at different hierarchy levels (e.g. project-level and model-level) now merge additively instead of the child config completely replacing the parent. by @canbekley in #1340information_schema.tags and information_schema.column_tags metadata fetches when table tags and column tags are not configured on a model. by @tejassp-db in #1387Full Changelog: v1.11.8...v1.12.0
feat: Implement row filter functionality by @sd-db in #1294
Full Changelog: v1.11.5...v1.12.0a1
feat: Add invocation_id to default query comment by @GuyEshdat in #1378
TestStreamingTableLiquidClusteringChanges by @sd-db in #1436Full Changelog: v1.11.7...v1.11.8
invocation_id to the default query comment (#1377)is_hudi or is_iceberg properties on relations without metadataMicrobatchConcurrency behavior-change warning firing on every run regardless of whether the project contained microbatch models (#1406)insert_overwrite will perform a dynamic insert overwrite warning on every insert_overwrite run on SQL warehouses; warn instead only when use_replace_on_for_insert_overwrite is enabled but the cluster's DBR version does not support REPLACE ON (#1305)use_materialization_v2 behavior-change warning firing on table, view, seed, and incremental materializations (#1089)use_managed_iceberg behavior-change warning firing on every run for projects that don't use Iceberg (#1266)contract.enforced: true is set on a materialized_view model (#1279)materialized_view models with databricks_tags silently going stale on dbt run. MaterializedViewAPI._describe_relation was not fetching information_schema.tags, so existing tags always parsed as empty, producing a spurious tag diff that routed the materialization to ALTER ... SET TAGS instead of REFRESH MATERIALIZED VIEW (#1419)dbt docs generate failing with RuntimeError: Tables contain columns with the same names ... but different types during catalog merge across schemas (#1392)feat: Add Notebook-scoped packages for command submits or notebook job run by @fedemgp in #1321
databricks_compute) by @trouze in #1355Full Changelog: v1.11.6...v1.11.7
table_format='iceberg') failing on named compute (databricks_compute) due to lazy DBR version caching (#1355)workflow_job Python model submission method failing with dictionary attribute error (#1360)TestWorkflowJob functional test that was unreachable on all profiles due to incorrect skip list, wrong model fixture, and invalid max_retries parameter (#1360)dbt run --empty failing with inline ref() / source() aliases (dbt-labs/dbt-adapters#660)databricks-sql-connector upper bound to <4.1.6, enabling users to opt into _respect_server_retry_after_header (available in connector 4.1.5) for server-directed retry behavior via connection_parameters (#1363)<1.11.9 to include dbt-core 1.11.8Enable concurrent microbatch execution by @wmjones in #1326
Full Changelog: v1.11.5...v1.11.6
MicrobatchConcurrency capability,
gated behind the use_concurrent_microbatch behavior flag (default: false).
Opt in via flags: {use_concurrent_microbatch: true} in dbt_project.yml
(#914)optimize on snapshots when liquid_clustered_by, zorder, or auto_liquid_cluster config is set, matching existing behavior for tables and incremental models (#1335)contract.enforced: false (#1343)optimize() call in table v2 materialization path (#1345)SHOW SCHEMAS commands, causing INVALID_IDENTIFIER errors (#1325)Fix: Retain multiple foreign-keys from one table to another after an incremental run by @Ewan-Keith in #1296
Full Changelog: v1.11.4...v1.11.5
feat: Add query-id to SQLQueryStatus by @colin-rogers-dbt in https://github.com/databricks/dbt-databricks/pull/1280
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.11.3...v1.11.4
query_id to SQLQueryStatus events to improve query tracing and debugginghard_deletes: invalidate incorrectly invalidating active records in snapshots (thanks @Zurbste!) (#1281)environment_version instead of deprecated client field. Users can now specify custom environment versions via python_job_config.environments. (#1286)Fix: escape and truncate default query tag values by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1273
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.11.2...v1.11.3
fix: pin click dependency version by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1265
Add support for hard_deletes='new_record' in snapshot materializations, enabling tracking of deleted source records with dedicated deletion records ma
hard_deletes='new_record' in snapshot materializations, enabling tracking of deleted source records with dedicated deletion records marked by dbt_is_deleted column (thanks @randypitcherii!) (#1176, #1263)
hard_deletes modes: ignore (default), invalidate, and new_recordnew_record mode creates deletion records with actual source column values and dbt_is_deleted=true for full audit trailinvalidate mode uses Delta Lake's WHEN NOT MATCHED BY SOURCE clause to set dbt_valid_to on deleted recordsdbt_is_deleted column for improved type safety and performance@@ prefix to system query tag keys (to keep them separate from user provided tags)Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.11.0...v1.11.1
Breaking Change: Requires Databricks Runtime 12.2 LTS or higher
insert_overwrite incremental strategy for SQL warehouses. This strategy now uses REPLACE ON syntax for all compute types (previously INSERT OVERWRITE). This behavior is gated behind behavior flag use_replace_on_for_insert_overwrite which defaults true (1025)table_format is set to iceberg. This behavior is gated behind behavior flag use_managed_iceberg which defaults to falseon_schema_change: sync_all_columns, dbt previously used positional column matching in INSERT statements, causing values to be inserted into wrong columns when column order changedINSERT BY NAME syntax to match columns by name instead of position, preventing data corruptionappend, insert_overwrite, replace_where, and merge (via table creation)CREATE OR REPLACE where appropriate, instead of DROP + CREATECREATE OR REPLACE instead of DROP + CREATE for managed Iceberg tablesNothing published for this version
Nothing published for this version
Nothing published for this version
chore: Updating the dbt-core pin for 1.10.latest by @zqureshi in https://github.com/databricks/dbt-databricks/pull/1306
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.18...v1.10.19
chore: Updating dbt-common and dbt-adapter pins for 1.10.x by @benc-db in https://github.com/databricks/dbt-databricks/pull/1300
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.17...v1.10.18
chore: Updating dbt-core pin by @benc-db in https://github.com/databricks/dbt-databricks/pull/1299
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.16...v1.10.17
feat: Bump dbt-core upper bound to allow for 1.10.16 on 1.10.latest by @QMalcolm in https://github.com/databricks/dbt-databricks/pull/1284
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.15...v1.10.16
Switch to a more reliable mechanism for checking schema existence (1261)
chore: Update dbt dependencies version ranges by @zqureshi in https://github.com/databricks/dbt-databricks/pull/1227
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.13...v1.10.14
Fix pydantic v2 deprecation warning "Valid config keys have changed in V2" (thanks @Korijn!) (1194)
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.12...v1.10.13
chore: Bump pyproject.toml dependencies by @emmyoop in https://github.com/databricks/dbt-databricks/pull/1178
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.11...v1.10.12
fix: Set correct cluster type on databricks connection by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1158
database attribute to build_catalog relation by @colin-rogers-dbt in https://github.com/databricks/dbt-databricks/pull/1170Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.10...v1.10.11
AS JSONDOCS: Update Databricks Workflow to match new naming Databricks Lakeflow Jobs by @excavator-matt in https://github.com/databricks/dbt-databricks/pull/
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.9...v1.10.10
Add column tag support for views by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1134
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.8...v1.10.9
ALTER TABLEREPLACE USING syntax being used for insert overwrite (1025)Add fallback logic for known error types for AS JSON by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1131
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.7...v1.10.8
DESCRIBE TABLE EXTENDED .. AS JSON for better reliability (1128)Fix AS JSON branching logic for MV/STs by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1123
Full Changelog: https://github.com/databricks/dbt-databricks/compare/1.10.6...v1.10.7
DESCRIBE TABLE EXTENDED .. AS JSON for STs when DBR version < 17.1. Do not use at all for MVs (not yet supported)Only run DESCRIBE TABLE EXTENDED .. AS JSON for DBR >= 16.2 by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1117
DESCRIBE TABLE EXTENDED .. AS JSON for DBR >= 16.2 by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1117Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.5...1.10.6
DESCRIBE TABLE EXTENDED .. AS JSON is now only used for DBR versions 16.2 and aboveFix inefficient query when getting column schema for MV/STs by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1080
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.4...v1.10.5
Wait for library installation on python submission by @ericj-db in https://github.com/databricks/dbt-databricks/pull/1031
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.2...v1.10.4
Fix for breaking change in dbt-adapters
Fix multiple null constraint situation by @benc-db in https://github.com/databricks/dbt-databricks/pull/1008
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.1...v1.10.2
catalogs.yml (1012)Fix: DBT Python Model Canceled Notebook Job Treated as Successful by @case-k-git in https://github.com/databricks/dbt-databricks/pull/985
requires_full_refresh on DatabricksRelationChangeSet by @geo-martino in https://github.com/databricks/dbt-databricks/pull/1000Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.0...v1.10.1
requires_full_refresh attribute after comment is changed on view and view_update_via_alter is true (thanks @geo-martino!)
(1000)Support databricks OAuth M2M auth type. Updated OAuth readme doc with instructions.(827)
While waiting for full documentation (coming shortly to the dbt Labs doc site), you can look at the discussion for the 1.10.0 alpha release in the discussion section for how to use the new features.
Nothing published for this version
Nothing published for this version
Nothing published for this version
quote columns for foreign key and primary key constraints, if quote: true in column config by @samuelberntzen in https://github.com/databricks/dbt-dat
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.10.0a1...v1.10.0a2
Small update to Monday's alpha.
Support databricks OAuth M2M auth type. Updated OAuth readme doc with instructions.(827)
Switch to using full_data_type column when using info schema for column info (950)
Readded missed language field for connections by @benc-db in https://github.com/databricks/dbt-databricks/pull/945
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.9.6...v1.9.7
Scope connection parameter creation (refactor for cleanliness) by @benc-db in https://github.com/databricks/dbt-databricks/pull/929
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.9.5...v1.9.6
Compress to one connection manager by @benc-db in https://github.com/databricks/dbt-databricks/pull/910
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.9.4...v1.9.5
auto_liquid_cluster config to enable Auto Liquid Clustering for Delta-based dbt models (thanks @ShaneMazur!) (935)We've heard numerous reports about timing out connection when getting 503s too quickly. Temporarily upper-bounding this dependency while we continue i
We've heard numerous reports about timing out connection when getting 503s too quickly. Temporarily upper-bounding this dependency while we continue investigation. Had to pull 1.9.3 because the published build was missing the pin :(.
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.9.2...v1.9.4
Yanked due to being published with the incorrect bits
Yanked due to being published with the incorrect bits
Adding missing 1.9 Snapshot behavior by @benc-db in https://github.com/databricks/dbt-databricks/pull/904
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.9.1...v1.9.2
Remove library restrictions where possible (pandas, pydantic) by @benc-db in https://github.com/databricks/dbt-databricks/pull/874
Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.9.0...v1.9.1
update set ... action with the explicit list of updates for when not matched by source (866) (thanks @mi-volodin).Prepare for python typing deprecations (837)
with schema evolution clause (requires Databricks Runtime 15.2 or above);when not matched by source clause, only for delete actionmatched, not matched and not matched by source condition clauses;matched and not matched steps can now be skipped;custom constraint type with an expression as the constraint (thanks @roydobbe). (792)include_full_name_in_path config boolean for external locations. This writes tables to {location_root}/{catalog}/{schema}/{table} (823)workflow_job submission method for python, which creates a long-lived Databricks Workflow instead of a one-time run (thanks @kdazzle!) (762)Full Changelog: https://github.com/databricks/dbt-databricks/compare/v1.8.6...v1.9.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →