You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-python. Each finding is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT (post-fix) behavior and stays red until THIS driver (databricks/databricks-sql-python) is fixed, then flips green as a tripwire.
Findings
RESULTFETCH-013 [thrift]: A terminal mid-stream FetchResults failure escapes the PEP 249 error hierarchy: attempt_request re-raises urllib3's MaxRetryError verbatim (thrift_backend.py:487-490) instead of wrapping it in RequestError, so an application catching databricks.sql.Error cannot catch or type-match a failed lazy fetch
failing test: test_error_handling_during_lazy_fetch (see the coverage PR diff under tests/)
Reproduce & Expected
RESULTFETCH-013 — Verify that a network or server error occurring mid-stream (during a lazy FetchResults call, not on the first call) is propagated correctly to the caller as an exception rather than silently returnin…
The behavior was first fixed in a DIFFERENT driver — reference PR: fix(kernel): decode a failed async status poll into the driver error databricks-sql-nodejs#608 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in databricks/databricks-sql-python; the reference PR is for cross-referencing the intended behavior, NOT a change to this repo.
Activity