[coverage] Conformance findings: SESSION-018
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- sql, typescript
- Domain
- backend-api-design, databases
Research direction
Start with the named failing test in the coverage PR under tests/ and inspect the Node.js driver's standard /api/2.0/sql/sessions CreateSession path. Confirm execution_mode=FAST is sent by default, then run the conformance case for SELECT 1 AS test_value and verify the session opens, executes, and closes with one row.
Written by the indexing model from the issue text.
Description
Summary
Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-nodejs. 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-nodejs) is fixed, then flips green as a tripwire.
Findings
- SESSION-018 [sea]: SEA CreateSession body omits execution_mode, so the session is not created in FAST mode; the driver sends only {warehouse_id} on POST /api/2.0/sql/sessions and therefore never receives server-issued session versions
- failing test:
sea session created in FAST execution mode — execution_mode=FAST on the standard /api/2.0/sql/sessions path [sea](see the coverage PR diff undertests/)
- failing test:
Reproduce & Expected
SESSION-018 — Validates that a driver creating a SEA (Statement Execution API) session requests FAST execution mode BY DEFAULT and that the session it gets back opens, executes a query and closes normally.
Reproduce:
SELECT 1 AS test_value
Expected (per the shared spec):
- completes without an exception
- result has exactly 1 row(s)
- [sea] exactly 1
CreateSessioncall(s) - [sea]
CreateSessionrequestexecution_mode== 'FAST'
Context
- The behavior was first fixed in a DIFFERENT driver — reference PR: https://github.com/databricks/databricks-sql-kernel/pull/331 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in databricks/databricks-sql-nodejs; the reference PR is for cross-referencing the intended behavior, NOT a change to this repo.
- Coverage PR carrying the reproducing xfail test(s): https://github.com/databricks/databricks-driver-test/pull/1663
- 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 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100