[coverage] Conformance findings: TELEMETRY-001,TELEMETRY-005

[peco-engineer-bot]

Summary

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

Findings

• TELEMETRY-001 [thrift]: terminal statement telemetry omits sql_operation.statement_type and sql_operation.execution_result; both fields exist in telemetry.SQLExecutionEvent but are never populated, so the backend cannot aggregate by statement classification or result-delivery shape
  • failing test: TestSuccessfulStatementExecutionEmitsTerminalOperationEvent (see the coverage PR diff under tests/)
• TELEMETRY-005 [thrift]: telemetry for an external-links (CloudFetch) result omits sql_operation.execution_result even though the same event reports chunk_details download bookkeeping, so EXTERNAL_LINKS vs INLINE_ARROW delivery shape is unreportable
  • failing test: TestTelemetryReportsExternalLinksDeliveryAndCompression (see the coverage PR diff under tests/)
• TELEMETRY-001: terminal statement telemetry omits sql_operation.statement_type and sql_operation.execution_result; both fields exist in the driver's telemetry.SQLExecutionEvent type but are never populated, so the backend cannot aggregate by statement classification or result-delivery shape

Context

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