[coverage] Conformance findings: SESSION-018

[peco-engineer-bot]

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 [thrift]: Thrift transport silently drops connect-time customHeaders: the header is applied only to driver-owned out-of-band telemetry/feature-flag requests, never to ExecuteStatement, so a header an auth proxy/gateway keys on is dropped with no error (SEA/kernel forwards it correctly)
  • failing test: custom HTTP header is sent on the query request (see the coverage PR diff under tests/)
• SESSION-018: Thrift transport silently drops connect-time customHeaders: a user-supplied custom HTTP header is applied only to driver-owned out-of-band telemetry/feature-flag requests, never to ExecuteStatement, so a header an auth proxy/gateway keys on is dropped with no error (SEA/kernel forwards it correctly)

Reproduce & Expected

SESSION-018 — A user-supplied custom HTTP header (the reference driver's per-header http.header.<Name>=<Value> connection-string convention) must be attached to the requests the driver sends to the workspace.

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: ExecuteStatement
      name: X-Databricks-Conformance
      equals: spec-session-018
  sea:
  - request_header:
      operation: ExecuteStatement
      name: X-Databricks-Conformance
      equals: spec-session-018

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/1109