You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-036 [sea]: SEA getColumns with a NULL catalog never returns: kernel metadata path fails with "Statement execution timed out" after ~10min, instead of one all-catalogs columns request returning cross-catalog rows (Thrift conforms with a single GetColumns RPC)
failing test: METADATA-036 — getColumns with null catalog returns columns from every catalog in ONE request [sea] (see the coverage PR diff under tests/)
I retested this on the latest release (@databricks/sql@2.4.0, kernel binary 1.3.0) against a current SQL warehouse. With useKernel: true, getColumns({ schemaName: 'nyctaxi', tableName: 'trips' }) with no catalog now returns in about 14 seconds. It gives the same 6 rows as the Thrift backend, from samples, the only catalog with that table here. It no longer times out.
I couldn't see how many requests the kernel sends for this call, so the METADATA-036 xfail test in the coverage PR linked above is the final check on the single-request part. Closing as fixed.
Activity
vuanhphung commentedon Oct 29, 2026
I retested this on the latest release (
@databricks/sql@2.4.0, kernel binary 1.3.0) against a current SQL warehouse. WithuseKernel: true,getColumns({ schemaName: 'nyctaxi', tableName: 'trips' })with no catalog now returns in about 14 seconds. It gives the same 6 rows as the Thrift backend, fromsamples, the only catalog with that table here. It no longer times out.I couldn't see how many requests the kernel sends for this call, so the METADATA-036 xfail test in the coverage PR linked above is the final check on the single-request part. Closing as fixed.