table-validator 0.1.2__tar.gz → 0.1.3__tar.gz

{table_validator-0.1.2/table_validator.egg-info → table_validator-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: table-validator
-Version: 0.1.2
+Version: 0.1.3
 Summary: CLI tool for validating data migrations between Azure (Blob Storage / SQL Database) and Databricks Delta Lake catalogs
 License: MIT
 Requires-Python: >=3.9
@@ -174,6 +174,14 @@ Everything lives outside the repo, under your home directory:
   by construction, since it's written under your home directory rather
   than the working directory.
 
+Optional: `DATABRICKS_RETRY_TIMEOUT_SECONDS` (a plain environment variable,
+not part of `config.yaml`) raises the CloudFetch HTTP retry timeout above
+its 300-second default. On a slow or unstable network, downloading a
+large row-hash result set can legitimately take longer than that, causing
+a `Retry request would exceed Retry policy max retry duration` failure
+even though the query itself succeeded. Set it higher (e.g. `900` for 15
+minutes) if you hit this on large tables.
+
 A future version will replace manual credential entry with Azure CLI /
 Service Principal auth and Databricks CLI / OAuth login, without changing
 the config file format or any command usage above.

{table_validator-0.1.2 → table_validator-0.1.3}/README.md

@@ -147,6 +147,14 @@ Everything lives outside the repo, under your home directory:
   by construction, since it's written under your home directory rather
   than the working directory.
 
+Optional: `DATABRICKS_RETRY_TIMEOUT_SECONDS` (a plain environment variable,
+not part of `config.yaml`) raises the CloudFetch HTTP retry timeout above
+its 300-second default. On a slow or unstable network, downloading a
+large row-hash result set can legitimately take longer than that, causing
+a `Retry request would exceed Retry policy max retry duration` failure
+even though the query itself succeeded. Set it higher (e.g. `900` for 15
+minutes) if you hit this on large tables.
+
 A future version will replace manual credential entry with Azure CLI /
 Service Principal auth and Databricks CLI / OAuth login, without changing
 the config file format or any command usage above.

{table_validator-0.1.2 → table_validator-0.1.3}/table_validator/connectors/databricks_connector.py

@@ -14,6 +14,7 @@ from __future__ import annotations
 import datetime
 import logging
 import numbers
+import os
 from typing import TYPE_CHECKING, Any, Dict, List, Optional, Sequence, Tuple
 
 import pandas as pd
@@ -97,6 +98,7 @@ class DatabricksConnector:
         host: Optional[str] = None,
         token: Optional[str] = None,
         http_path: Optional[str] = None,
+        retry_timeout_seconds: Optional[float] = None,
     ) -> None:
         """
         host/token/http_path must be resolved by the caller before
@@ -104,11 +106,27 @@ class DatabricksConnector:
         get_databricks_token() for the token, and config.databricks.
         workspace_url/http_path for the rest. This connector does not
         read credentials from the environment itself.
+
+        retry_timeout_seconds overrides databricks-sql-connector's
+        CloudFetch HTTP retry policy (_retry_stop_after_attempts_duration),
+        which otherwise defaults to 300 seconds. On a slow or unstable
+        network, downloading a large row-hash result set can legitimately
+        take longer than that, causing a hard
+        "Retry request would exceed Retry policy max retry duration"
+        failure even though the query itself succeeded - raising this
+        gives a slow-but-working connection more time instead of giving
+        up. Falls back to the DATABRICKS_RETRY_TIMEOUT_SECONDS environment
+        variable, then the connector's own default, if not given.
         """
 
         self._host = host
         self._token = token
         self._http_path = http_path
+        self._retry_timeout_seconds = retry_timeout_seconds or (
+            float(os.environ["DATABRICKS_RETRY_TIMEOUT_SECONDS"])
+            if os.environ.get("DATABRICKS_RETRY_TIMEOUT_SECONDS")
+            else None
+        )
 
         if not self._host or not self._token:
             raise ValueError(
@@ -138,11 +156,17 @@ class DatabricksConnector:
 
         try:
 
-            self._connection = sql.connect(
-                server_hostname=self._host,
-                http_path=self._http_path,
-                access_token=self._token,
-            )
+            connect_kwargs: Dict[str, Any] = {
+                "server_hostname": self._host,
+                "http_path": self._http_path,
+                "access_token": self._token,
+            }
+            if self._retry_timeout_seconds is not None:
+                connect_kwargs["_retry_stop_after_attempts_duration"] = (
+                    self._retry_timeout_seconds
+                )
+
+            self._connection = sql.connect(**connect_kwargs)
 
             with self._connection.cursor() as cursor:
                 cursor.execute("SELECT 1")

{table_validator-0.1.2 → table_validator-0.1.3/table_validator.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: table-validator
-Version: 0.1.2
+Version: 0.1.3
 Summary: CLI tool for validating data migrations between Azure (Blob Storage / SQL Database) and Databricks Delta Lake catalogs
 License: MIT
 Requires-Python: >=3.9
@@ -174,6 +174,14 @@ Everything lives outside the repo, under your home directory:
   by construction, since it's written under your home directory rather
   than the working directory.
 
+Optional: `DATABRICKS_RETRY_TIMEOUT_SECONDS` (a plain environment variable,
+not part of `config.yaml`) raises the CloudFetch HTTP retry timeout above
+its 300-second default. On a slow or unstable network, downloading a
+large row-hash result set can legitimately take longer than that, causing
+a `Retry request would exceed Retry policy max retry duration` failure
+even though the query itself succeeded. Set it higher (e.g. `900` for 15
+minutes) if you hit this on large tables.
+
 A future version will replace manual credential entry with Azure CLI /
 Service Principal auth and Databricks CLI / OAuth login, without changing
 the config file format or any command usage above.

{table_validator-0.1.2 → table_validator-0.1.3}/table_validator.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.1.2",
+  "tag": "0.1.3",
   "distance": 0,
-  "node": "g43988f9f51a097e239c49384ab59f00fec5851ab",
+  "node": "g8f7a326158b935508f39bc9369245d7817f1dc89",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-27"

{table_validator-0.1.2 → table_validator-0.1.3}/tests/test_databricks_connector.py

@@ -8,9 +8,12 @@ so these tests verify SQL-generation logic and result parsing only.
 
 from __future__ import annotations
 
+from unittest.mock import MagicMock
+
 import pandas as pd
 import pytest
 
+import table_validator.connectors.databricks_connector as databricks_connector_module
 from table_validator.connectors.databricks_connector import DatabricksConnector
 
 
@@ -402,3 +405,78 @@ def test_get_row_detail_for_row_numbers_wraps_exceptions(monkeypatch):
             row_numbers=[2],
             value_columns=["id"],
         )
+
+
+# ---------------------------------------------------------------------------
+# connect(): retry timeout override for slow/unstable CloudFetch downloads.
+# ---------------------------------------------------------------------------
+def test_connect_omits_retry_kwarg_by_default(monkeypatch):
+    """Without an explicit retry_timeout_seconds or
+    DATABRICKS_RETRY_TIMEOUT_SECONDS, connect() must not pass
+    _retry_stop_after_attempts_duration at all, preserving
+    databricks-sql-connector's own default (300s)."""
+    monkeypatch.delenv("DATABRICKS_RETRY_TIMEOUT_SECONDS", raising=False)
+    captured = {}
+
+    def fake_connect(**kwargs):
+        captured.update(kwargs)
+        return MagicMock()
+
+    monkeypatch.setattr(databricks_connector_module.sql, "connect", fake_connect)
+    connector = _connector()
+
+    connector.connect()
+
+    assert "_retry_stop_after_attempts_duration" not in captured
+
+
+def test_connect_passes_explicit_retry_timeout_seconds(monkeypatch):
+    monkeypatch.delenv("DATABRICKS_RETRY_TIMEOUT_SECONDS", raising=False)
+    captured = {}
+
+    def fake_connect(**kwargs):
+        captured.update(kwargs)
+        return MagicMock()
+
+    monkeypatch.setattr(databricks_connector_module.sql, "connect", fake_connect)
+    connector = DatabricksConnector(
+        host="h", token="t", http_path="p", retry_timeout_seconds=900.0
+    )
+
+    connector.connect()
+
+    assert captured["_retry_stop_after_attempts_duration"] == 900.0
+
+
+def test_connect_falls_back_to_retry_timeout_env_var(monkeypatch):
+    monkeypatch.setenv("DATABRICKS_RETRY_TIMEOUT_SECONDS", "1200")
+    captured = {}
+
+    def fake_connect(**kwargs):
+        captured.update(kwargs)
+        return MagicMock()
+
+    monkeypatch.setattr(databricks_connector_module.sql, "connect", fake_connect)
+    connector = _connector()
+
+    connector.connect()
+
+    assert captured["_retry_stop_after_attempts_duration"] == 1200.0
+
+
+def test_connect_explicit_arg_takes_priority_over_env_var(monkeypatch):
+    monkeypatch.setenv("DATABRICKS_RETRY_TIMEOUT_SECONDS", "1200")
+    captured = {}
+
+    def fake_connect(**kwargs):
+        captured.update(kwargs)
+        return MagicMock()
+
+    monkeypatch.setattr(databricks_connector_module.sql, "connect", fake_connect)
+    connector = DatabricksConnector(
+        host="h", token="t", http_path="p", retry_timeout_seconds=600.0
+    )
+
+    connector.connect()
+
+    assert captured["_retry_stop_after_attempts_duration"] == 600.0