[coverage] Conformance findings: ERRORRECOV-013
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- node.js, typescript
- Domain
- api, backend, networking
Research direction
Start with the ExecuteStatement path and the retryableThriftMethods entry mentioned in the report, then compare it with the SEA kernel handling. Review the expected-failure tests in the linked coverage PR and the reference driver PR. Done means a raw TCP connection close is retried for ExecuteStatement in both paths, rather than failing after one attempt.
Written by the indexing model from the issue text.
Description
Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-nodejs.
Each is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT behavior and stays red until this driver is fixed.
- ERRORRECOV-013: Thrift does not retry a transport-level failure (TCP connection close) on ExecuteStatement — surfaces the error after a single attempt (ExecuteStatement excluded from retryableThriftMethods)
- ERRORRECOV-013: SEA kernel does not retry a raw connection-close on ExecuteStatement — fails after 1 attempt with 'HTTP request failed after 1 attempts' despite tagging the error retryable:true
Reference driver PR: https://github.com/adbc-drivers/databricks/pull/373
Coverage PR (reproducing xfail tests): https://github.com/databricks/databricks-driver-test/pull/895
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 50
- Avg merge
- 13h 46m
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databricks/databricks-sql-nodejs
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
engineer-bot
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
databricks/databricks-sql-nodejs#274 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100