[coverage] Conformance findings: SESSION-018

Open
#525 0 comments 0 reactions 0 assignees View on GitHub

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

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 under tests/)

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 CreateSession call(s)
  • [sea] CreateSession request execution_mode == 'FAST'

Context

Dominant language
TypeScript
Stars
36
Forks
50
Avg merge
13h 46m
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/databricks-sql-nodejs

All issues in databricks/databricks-sql-nodejs

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.