Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[coverage] Conformance findings: SESSION-018

未关闭
#525 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
sql, typescript

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
TypeScript
星标
36
派生
50
平均合并
5 小时 56 分钟
30 天内合并 PR
9

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

databricks/databricks-sql-nodejs 的其他 Issue

查看 databricks/databricks-sql-nodejs 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。