[coverage] Conformance findings: DIRECTRES-001,DIRECTRES-002,DIRECTRES-003,DIRECTRES-004,DIRECTRES-011
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with the expected-failure tests in the coverage PR and compare their assertions for DIRECTRES-001 through DIRECTRES-011 with the reference driver PR. Trace the native SEA ExecuteStatement request and the handling of CLOSED results and multi-chunk responses. Done means the xfail tests pass without a positive wait_timeout when direct results are enabled, including the redundant-close and truncation cases.
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-python.
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.
- DIRECTRES-001: native SEA backend sends a positive wait_timeout on ExecuteStatement; ES-2034600 fix omits it when direct results are on
- DIRECTRES-002: native SEA backend sends a positive wait_timeout on ExecuteStatement; ES-2034600 fix omits it when direct results are on
- DIRECTRES-003: native SEA backend sends a positive wait_timeout on ExecuteStatement; ES-2034600 fix omits it when direct results are on
- DIRECTRES-004: native SEA backend sends a positive wait_timeout; the CLOSED-as-success skip-redundant-close contract cannot be conformed (ES-2034600)
- DIRECTRES-011: SEA ExecuteStatement sends positive wait_timeout instead of omitting it; multi-chunk result can be silently truncated to chunk 0 under sync-hybrid (ES-2034600)
Reference driver PR: https://github.com/adbc-drivers/databricks/pull/566
Coverage PR (reproducing xfail tests): https://github.com/databricks/databricks-driver-test/pull/786
- Dominant language
- Python
- Stars
- 233
- Forks
- 152
- Avg merge
- 21h 5m
- Merged PRs (30d)
- 10
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-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
All issues in databricks/databricks-sql-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·