Skip to content

Allow databricks-sql-connector >=4.2 to pick up thrift 0.22 fix (PR #733) #1445

@JordyForNow

Description

@JordyForNow

Summary

dbt-databricks 1.11.7 (and the 1.12.0a1 alpha) still pin
databricks-sql-connector[pyarrow]<4.1.6,>=4.1.1. This blocks adoption of
databricks-sql-connector 4.2.6, which is the first release containing the
fix from databricks/databricks-sql-python#733
that bumps the thrift requirement to >=0.22,<0.23.

The thrift bump is needed in environments where dbt-databricks is installed
alongside other tooling (in our case sqlfluff + sqlfluff-templater-dbt)
that is incompatible with the older thrift<0.21 constraint inherited from
connector 4.1.x. Today our only workaround is a [tool.uv] override-dependencies = ["thrift==0.22.0"] entry in pyproject.toml, which
forces a thrift version that violates connector 4.1.x's declared range.

Request

Widen the databricks-sql-connector upper bound to allow >=4.2.6 (e.g.
<5.0.0) so that:

  • thrift>=0.22 resolves naturally for downstream consumers
  • The override hack can be removed
  • We pick up other 4.2.x improvements

Context

Happy to send a PR if helpful — wanted to check first whether the cap on
<4.1.6 is intentional (e.g. known incompatibility with 4.2.x APIs) or
simply hasn't been revisited yet.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions