[coverage] Conformance findings: SESSION-018

Ouverte
#525 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
68/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
sql, typescript

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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

Langage dominant
TypeScript
Étoiles
36
Forks
50
Merge moyen
13 h 46 min
PR mergées (30 j)
9

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de databricks/databricks-sql-nodejs

Toutes les issues de databricks/databricks-sql-nodejs

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.