[coverage] Conformance findings: METADATA-035,METADATA-036

coverage PR の tests/ diff から始め、METADATA-035 の session.getTables() を追跡して、空の tableTypes の動作を確認します。次に、METADATA-036 の SEA メタデータパスと、その statement のクローズ処理を調べます。tableTypes=[] の動作と CLOSED メタデータ statements の両方について、参照されている xfail ケースが green になれば完了です。

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

• METADATA-035 [thrift, sea]: session.getTables() treats an empty tableTypes array as "match none" and returns 0 rows instead of behaving like a null filter and matching ALL table types (adbc-drivers/hiveserver2#72)
  • failing test: getTables — tableTypes=[] (empty, non-null) matches ALL table types [xfail: driver bug] [thrift], getTables — tableTypes=[] (empty, non-null) matches ALL table types [xfail: driver bug] [sea] (see the coverage PR diff under tests/)
• METADATA-036 [sea]: the SEA metadata path sends a redundant CloseStatement DELETE even when the metadata ExecuteStatement response reported status.state=CLOSED; the driver's regular-query path honors the terminal state correctly, so this is metadata-specific
  • failing test: METADATA-036 — metadata statement close honors ExecuteStatement status.state [sea] (see the coverage PR diff under tests/)

Context

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