[coverage] Conformance findings: STATEMENT-022 #472

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

• STATEMENT-022 [thrift]: Thrift does not deduplicate concurrent Operation.cancel() calls: three simultaneous cancels send three CancelOperation RPCs instead of the single deduped RPC the reference driver sends
  • failing test: STATEMENT-022 — three simultaneous cancel() calls: no deadlock, dedup per protocol [thrift] (see the coverage PR diff under tests/)

Reproduce & Expected

STATEMENT-022 — Validates driver handles multiple threads calling CancelOperation on same statement without deadlock or crash.

Reproduce:

SELECT a.*, b.* FROM main.tpcds_sf1_delta.catalog_returns a CROSS JOIN range(1, 10000) b ORDER BY a.cr_order_number, b.id

Expected (per the shared spec):

• completes without an exception
• [thrift] exactly 1 CancelOperation call(s)
• [sea] between 1 and 3 CancelStatement call(s)

Context

• The behavior was first fixed in a DIFFERENT driver — reference PR: Tag staging, decompression, and cancellation errors for telemetry databricks-sql-go#419 — 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/1015