[coverage] Conformance findings: LOGGING-005

Inizia con i test LOGGING-005 falliti nel coverage PR diff sotto tests/ e confronta il loro comportamento atteso con la PR di riferimento databricks-odbc. Poi traccia i corrispondenti percorsi di logging Thrift e SEA in questo driver Node.js ed esegui i test di riproduzione; il lavoro è completato quando entrambi i backend soddisfano il comportamento di logging previsto e i test diventano verdi.

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

• LOGGING-005 [thrift]: Thrift backend emits one "Fetched chunk of size: N from operation with id: …" record per fetch at LogLevel.debug (DEBUG volume scales with fetch count) and emits no aggregate per-result-set summary at teardown; the exported LogLevel enum has no trace member, so there is no less-verbose level to demote the per-fetch detail to.
  • failing test: LOGGING-005 — driver bug: per-fetch record emitted at DEBUG with no per-result-set summary [thrift] (see the coverage PR diff under tests/)
• LOGGING-005 [sea]: SEA kernel backend emits one "Fetched chunk of size: N from operation with id: …" record per fetch at LogLevel.debug (DEBUG volume scales with fetch count) and emits no aggregate per-result-set summary at teardown, including for a result set abandoned after 2 of 100 rows; the exported LogLevel enum has no trace member, so there is no less-verbose level to demote the per-fetch detail to.
  • failing test: LOGGING-005 — driver bug: per-fetch record emitted at DEBUG with no per-result-set summary [sea] (see the coverage PR diff under tests/)
• LOGGING-005: At LogLevel.debug the driver logs one "Fetched chunk of size: N from operation with id: …" record per fetch (unbounded in fetch count — 1-row metadata-browsing rowsets flood the log) and emits no aggregate per-result-set summary at teardown; the per-fetch detail also has no less-verbose level to be demoted to because the exported LogLevel enum has no trace member. Affects both the Thrift backend and the SEA kernel.

Context

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