[coverage] Conformance findings: TELEMETRY-002

[peco-engineer-bot]

Summary

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against adbc-drivers/databricks. 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 (adbc-drivers/databricks) is fixed, then flips green as a tripwire.

Findings

• TELEMETRY-002 [thrift]: Abandoned (unread, disposed) result set stamps result_set_consumption_latency_millis in the terminal EXECUTE_STATEMENT telemetry record: DatabricksStatement.EmitTelemetry calls ctx.RecordResultsConsumed() unconditionally, so caller think-time from statement start to handle release is reported as consumption latency; the field should be absent when the stream was never consumed
  • failing test: AbandonedResultSetStillFinalizesStatementTelemetry (see the coverage PR diff under tests/)
• TELEMETRY-002: Abandoned (unread, disposed) result set stamps result_set_consumption_latency_millis in the terminal EXECUTE_STATEMENT telemetry record: DatabricksStatement.EmitTelemetry calls ctx.RecordResultsConsumed() unconditionally, so caller think-time from statement start to handle release is reported as consumption latency, skewing that metric's aggregates; the field should be absent when the stream was never consumed

Context

• The behavior was first fixed in a DIFFERENT driver — reference PR: https://github.com/databricks/databricks-sql-kernel/pull/274 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in adbc-drivers/databricks; 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/1451