[coverage] Conformance findings: SESSION-017

Start with the SESSION-017 xfail test in the coverage PR diff under tests/ and reproduce it with SELECT 1 AS test_value. Trace the TypeScript driver path for ConnectionOptions.customHeaders and compare the request assertions for OpenSession and ExecuteStatement. Done means the test passes with both configured headers sent on session-open and the expected header sent on statement requests.

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-017 [thrift]: ConnectionOptions.customHeaders is accepted but silently dropped: no configured custom header appears on the Thrift OpenSession or ExecuteStatement request on the wire
  • failing test: custom HTTP headers are sent on every request — session open and statement [thrift] [xfail: driver drops customHeaders] (see the coverage PR diff under tests/)

Reproduce & Expected

SESSION-017 — Validates that connection-configured custom HTTP headers are actually SENT on every request the driver makes to the workspace — both the session-open request and subsequent statement requests — and t…

Reproduce:

SELECT 1 AS test_value

Expected (per the shared spec):

• completes without an exception
• result has exactly 1 row(s)
• full assertion contract:

result:
- no_exception: true
- row_count: 1
protocol:
  thrift:
  - request_header:
      method: OpenSession
      name: X-Databricks-Spec-Header-A
      equals: session-017-a
  - request_header:
      method: OpenSession
      name: X-Databricks-Spec-Header-B
      equals: session-017-b
  - request_header:
      method: ExecuteStatement
      name: X-Databricks-Spec-Header-A
      equals: session-017-a
  sea:
  - request_header:
      operation: CreateSession
      name: X-Databricks-Spec-Header-A
      equals: session-017-a
  - request_header:
      operation: CreateSession
      name: X-Databricks-Spec-Header-B
      equals: session-017-b
  - request_header:
      operation: ExecuteStatement
      name: X-Databricks-Spec-Header-A
      equals: session-017-a

Context

• The behavior was first fixed in a DIFFERENT driver — reference PR: https://github.com/databricks/databricks-odbc/pull/180 — 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/1181