databricks-sql-connector 4.1.0__tar.gz → 4.1.1__tar.gz

{databricks_sql_connector-4.1.0 → databricks_sql_connector-4.1.1}/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release History
 
+# 4.1.1 (2025-08-21)
+- Add documentation for proxy support (databricks/databricks-sql-python#680 by @vikrantpuppala)
+- Fix compatibility with urllib3<2 and add CI actions to improve dependency checks (databricks/databricks-sql-python#678 by @vikrantpuppala)
+
 # 4.1.0 (2025-08-18)
 - Removed Codeowners (databricks/databricks-sql-python#623 by @jprakash-db)
 - Azure Service Principal Credential Provider (databricks/databricks-sql-python#621 by @jprakash-db)

{databricks_sql_connector-4.1.0 → databricks_sql_connector-4.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: databricks-sql-connector
-Version: 4.1.0
+Version: 4.1.1
 Summary: Databricks SQL Connector for Python
 License: Apache-2.0
 Author: Databricks
@@ -40,6 +40,8 @@ The Databricks SQL Connector for Python allows you to develop Python application
 
 This connector uses Arrow as the data-exchange format, and supports APIs (e.g. `fetchmany_arrow`) to directly fetch Arrow tables. Arrow tables are wrapped in the `ArrowQueue` class to provide a natural API to get several rows at a time. [PyArrow](https://arrow.apache.org/docs/python/index.html) is required to enable this and use these APIs, you can install it via  `pip install pyarrow` or `pip install databricks-sql-connector[pyarrow]`.
 
+The connector includes built-in support for HTTP/HTTPS proxy servers with multiple authentication methods including basic authentication and Kerberos/Negotiate authentication. See `docs/proxy.md` and `examples/proxy_authentication.py` for details.
+
 You are welcome to file an issue here for general use cases. You can also contact Databricks Support [here](help.databricks.com).
 
 ## Requirements

{databricks_sql_connector-4.1.0 → databricks_sql_connector-4.1.1}/README.md

@@ -7,6 +7,8 @@ The Databricks SQL Connector for Python allows you to develop Python application
 
 This connector uses Arrow as the data-exchange format, and supports APIs (e.g. `fetchmany_arrow`) to directly fetch Arrow tables. Arrow tables are wrapped in the `ArrowQueue` class to provide a natural API to get several rows at a time. [PyArrow](https://arrow.apache.org/docs/python/index.html) is required to enable this and use these APIs, you can install it via  `pip install pyarrow` or `pip install databricks-sql-connector[pyarrow]`.
 
+The connector includes built-in support for HTTP/HTTPS proxy servers with multiple authentication methods including basic authentication and Kerberos/Negotiate authentication. See `docs/proxy.md` and `examples/proxy_authentication.py` for details.
+
 You are welcome to file an issue here for general use cases. You can also contact Databricks Support [here](help.databricks.com).
 
 ## Requirements

{databricks_sql_connector-4.1.0 → databricks_sql_connector-4.1.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "databricks-sql-connector"
-version = "4.1.0"
+version = "4.1.1"
 description = "Databricks SQL Connector for Python"
 authors = ["Databricks <databricks-sql-connector-maintainers@databricks.com>"]
 license = "Apache-2.0"

{databricks_sql_connector-4.1.0 → databricks_sql_connector-4.1.1}/src/databricks/sql/__init__.py

@@ -68,7 +68,7 @@ DATETIME = DBAPITypeObject("timestamp")
 DATE = DBAPITypeObject("date")
 ROWID = DBAPITypeObject()
 
-__version__ = "4.1.0"
+__version__ = "4.1.1"
 USER_AGENT_NAME = "PyDatabricksSqlConnector"
 
 # These two functions are pyhive legacy

{databricks_sql_connector-4.1.0 → databricks_sql_connector-4.1.1}/src/databricks/sql/backend/sea/utils/http_client.py

@@ -255,7 +255,10 @@ class SeaHttpClient:
             ) as response:
                 # Handle successful responses
                 if 200 <= response.status < 300:
-                    return response.json()
+                    if response.data:
+                        return json.loads(response.data.decode())
+                    else:
+                        return {}
 
                 error_message = f"SEA HTTP request failed with status {response.status}"
                 raise Exception(error_message)

{databricks_sql_connector-4.1.0 → databricks_sql_connector-4.1.1}/src/databricks/sql/common/unified_http_client.py

@@ -10,6 +10,14 @@ from urllib3 import PoolManager, ProxyManager
 from urllib3.util import make_headers
 from urllib3.exceptions import MaxRetryError
 
+# Compatibility import for different urllib3 versions
+try:
+    # If urllib3~=2.0 is installed
+    from urllib3 import BaseHTTPResponse
+except ImportError:
+    # If urllib3~=1.0 is installed
+    from urllib3 import HTTPResponse as BaseHTTPResponse
+
 from databricks.sql.auth.retry import DatabricksRetryPolicy, CommandType
 from databricks.sql.exc import RequestError
 from databricks.sql.common.http import HttpMethod
@@ -222,7 +230,7 @@ class UnifiedHttpClient:
         url: str,
         headers: Optional[Dict[str, str]] = None,
         **kwargs,
-    ) -> Generator[urllib3.BaseHTTPResponse, None, None]:
+    ) -> Generator[BaseHTTPResponse, None, None]:
         """
         Context manager for making HTTP requests with proper resource cleanup.
 
@@ -233,7 +241,7 @@ class UnifiedHttpClient:
             **kwargs: Additional arguments passed to urllib3 request
 
         Yields:
-            urllib3.BaseHTTPResponse: The HTTP response object
+            BaseHTTPResponse: The HTTP response object
         """
         logger.debug(
             "Making %s request to %s", method, urllib.parse.urlparse(url).netloc
@@ -270,7 +278,7 @@ class UnifiedHttpClient:
         url: str,
         headers: Optional[Dict[str, str]] = None,
         **kwargs,
-    ) -> urllib3.BaseHTTPResponse:
+    ) -> BaseHTTPResponse:
         """
         Make an HTTP request.
 
@@ -281,7 +289,7 @@ class UnifiedHttpClient:
             **kwargs: Additional arguments passed to urllib3 request
 
         Returns:
-            urllib3.BaseHTTPResponse: The HTTP response object with data and metadata pre-loaded
+            BaseHTTPResponse: The HTTP response object with data and metadata pre-loaded
         """
         with self.request_context(method, url, headers=headers, **kwargs) as response:
             # Read the response data to ensure it's available after context exit