topic ERROR: No matching distribution found for databricks-connect==7.3.34 in Data Engineering

ERROR: No matching distribution found for databricks-connect==7.3.34

vk217 — Thu, 21 Jul 2022 17:24:18 GMT

Previously, our databricks-connect was using 7.3.34 and the builds in pipenv and the builds were successful. As of today the builds are failing with error that the version 7.3.34 no longer exists.

Is there a reason this version is no longer supported. What version should be upgrade to?

[pipenv.exceptions.InstallError]: ERROR: Could not find a version that satisfies the requirement databricks-connect==7.3.34 (from versions: 5.5.3, 6.4.0, 6.4.1, 6.4.2, 6.4.28, 6.4.49, 6.6.0, 7.1.0, 7.1.14, 7.3.5, 7.3.9, 7.3.12, 7.3.14, 7.3.19, 7.3.27, 7.3.28, 7.3.29, 7.3.30, 7.3.35, 7.3.36, 7.3.37, 7.3.39, 7.3.40, 7.3.41, 7.3.42, 7.3.43, 7.3.45, 8.1.11, 8.1.14, 9.1.8, 9.1.9, 9.1.10, 9.1.11, 9.1.12, 9.1.13, 9.1.14, 9.1.15, 9.1.16, 9.1.17, 9.1.18, 9.1.20, 10.4.0b0, 10.4.6, 10.4.8)

Re: ERROR: No matching distribution found for databricks-connect==7.3.34

Atanu — Thu, 21 Jul 2022 18:01:46 GMT

Hello @Vikas B this is the release note -

https://docs.databricks.com/release-notes/dbconnect/index.html

also,

Only the following Databricks Runtime versions are supported:
- Databricks Runtime 10.4 LTS ML, Databricks Runtime 10.4 LTS
- Databricks Runtime 9.1 LTS ML, Databricks Runtime 9.1 LTS
- Databricks Runtime 7.3 LTS ML, Databricks Runtime 7.3 LTS
- Databricks Runtime 6.4 ML, Databricks Runtime 6.4

https://docs.databricks.com/dev-tools/databricks-connect.html#requirements

Re: ERROR: No matching distribution found for databricks-connect==7.3.34

vk217 — Thu, 21 Jul 2022 21:16:25 GMT

So the Databricks Connect release notes includes 7.3.34.

Databricks Connect 7.3.34

February 8, 2022

Databricks Connect client update to support Databricks Runtime 7.3 maintenance release of February 8, 2022.

Re: ERROR: No matching distribution found for databricks-connect==7.3.34

-werners- — Mon, 25 Jul 2022 07:53:30 GMT

why do you specify the exact version? databricks-connect documentation states specifically to add a wildcard:

"Always specify

databricks-connect==X.Y.*

instead of

databricks-connect=X.Y

, to make sure that the newest package is installed."