Skip to content

[v3-3-test] Pin databricks-sql-connector>=4.0.0 in generated constraints (#69863) #69871

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eladkal merged 1 commit into from
Jul 14, 2026
+6 −1
Merged

[v3-3-test] Pin databricks-sql-connector>=4.0.0 in generated constraints (#69863) #69871

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion scripts/in_container/run_generate_constraints.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -398,10 +398,15 @@ def generate_constraints_pypi_providers(config_params: ConfigParams) -> None:
# does not yet carry this cap, so we mirror it here so PyPI constraints stay installable
# until the SQLAlchemy fix is released. Tracked upstream at
# https://github.com/sqlalchemy/sqlalchemy/issues/13306
#
# * databricks-sql-connector>=4.0.0 - added to keep databricks-sql-connector from downgrading
# because of https://github.com/apache/thrift/pull/3584 - which shipped thrift 0.24.0. Older
# versions of databricks-sql-connector do not have the thrift<=0.23.0 limitation, so the
# resolver preferred the latest thrift over the latest connector and downgraded the connector.
# This is tracked in https://github.com/databricks/databricks-sql-python/issues/859
additional_constraints_for_highest_resolution: list[str] = [
"pyarrow>=22.0.0; python_version >= '3.14'",
"pymysql>=1.0.3,<1.2",
"databricks-sql-connector>=4.0.0",
]

result = run_command(
Expand Down
Loading