Skip to content

chore(deps): raise databricks-sql-connector upper bound to <4.3.1 to support 4.3.0#1518

Open
sd-db wants to merge 1 commit into
mainfrom
sd-db/chore/bump-connector-4.3.0
Open

chore(deps): raise databricks-sql-connector upper bound to <4.3.1 to support 4.3.0#1518
sd-db wants to merge 1 commit into
mainfrom
sd-db/chore/bump-connector-4.3.0

Conversation

@sd-db

@sd-db sd-db commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

Summary

Raises the databricks-sql-connector[pyarrow] upper bound from <4.2.7 to <4.3.1 and bumps the lock to 4.3.0 (released 2026-06-12 — the latest good release; 4.2.7 was yanked upstream, which is why the ceiling was previously <4.2.7).

No-code-change bump:

  • 4.3.0's only additions are an opt-in Rust use_kernel backend and a thrift-0.23.0 revert; the default Thrift backend is unchanged.
  • The new [kernel] extra is not pulled in by [pyarrow], and the connector API dbt uses (Connection, Cursor, __version__, exc.Error) is unchanged.
  • requirements.lowest-direct.txt is left untouched — only the ceiling moved; the floor (>=4.1.1) is unchanged.

Testing

  • Unit suite against 4.3.0: 1191 passed, 6 skipped
  • Functional smoke on a SQL warehouse (databricks_uc_sql_endpoint): connection validation + table materialization + all column types — 4 passed

@sd-db sd-db requested a review from jprakash-db as a code owner June 15, 2026 13:00
@sd-db sd-db force-pushed the sd-db/chore/bump-connector-4.3.0 branch from 6f5810d to b9b03a7 Compare June 15, 2026 13:01
@github-actions

Copy link
Copy Markdown

Coverage report

This PR does not seem to contain any modification to coverable code.

@sd-db

sd-db commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator Author

/integration-test

@github-actions

Copy link
Copy Markdown

Integration tests dispatched for PR #1518 by @sd-db. Track progress in the Actions tab.

@github-actions

Copy link
Copy Markdown

Integration results for PR #1518 — UC cluster ✅ success · SQL warehouse ✅ success · All-purpose cluster ✅ success · Shard coverage ✅ success

Run details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants