[SEA-NodeJS] (5/8) executeStatement + openSession (sessionConfig, initialCatalog/Schema)

[msrathore-db]

Stack

Linear stack of 8 PRs landing the M0 + M1 Phase 1 SEA NodeJS work. Merge in order from base ↑ to tip. The tip branch (msrathore/sea-auth-u2m, PR #383) is the single snapshot containing everything in flight — point your test or benchmark harness at it for an end-to-end check.

Pos	PR	Branch	Scope
1/8	#378	sea-abstraction	IBackend / ISessionBackend / IOperationBackend interfaces
2/8	#380	sea-napi-binding	TS loader + build script for the kernel-provided .node artifact
3/8	#377	sea-errors-logging	Kernel ErrorCode → JS error-class mapping (M0 minimum)
4/8	#379	sea-auth	PAT auth via useSEA: true
5/8	#382	sea-execution	executeStatement + openSession (sessionConfig, initialCatalog/Schema)
6/8	#381	sea-results	CloudFetch + Inline Arrow result fetching
7/8	#384	sea-operation	cancel / close / finished lifecycle + INTERVAL parity + napi-relocation acceptance (absorbed sea-integration content)
8/8	#383	sea-auth-u2m← TIP	M1 Phase 1 OAuth M2M + U2M (5 review rounds, ZERO HIGH at close)

Companion kernel stack (databricks/databricks-sql-kernel): 8 PRs — root #26 (async-public-api) → #27 → #25 → #29 → #28 → #30 → #24 → #23 (tip).

Policy: new PRs always stack on the current tip. No sibling/parallel topology. No force-pushes on existing PRs unless absolutely necessary; if a PR's content is wrong, add a fix-up commit on top of the stack tip rather than rewriting history.

---

This PR is position 5/8.

Summary

Implements SeaSessionBackend.executeStatement() and openSession() — the core SEA execution surface. Honors sessionConfig, initialCatalog, initialSchema on connect.

Size note (1439 LOC)

openSession + executeStatement are tightly coupled; splitting them creates a non-functional intermediate state. Reviewer-friendly approach: read commit-by-commit; each commit is a coherent slice of the feature.

Downstream fixes / reviewer note

• This PR is the initial M0 execution path and uses the blocking native executeStatement shape. The real Thrift runAsync parity fix lands later in feat(sea): execute statements asynchronously (submit + poll) for Thrift runAsync parity #406, which switches SEA to submitStatement + polling and restores real status/progress/mid-run cancel behavior.
• Statement-option and parameter gaps visible here are fixed downstream: feat(sea): Thrift-parity — params, intervals, getInfo, SQL-error class, input validation + queryTags #403 wires positional/named params, queryTimeout, input validation, getInfo, SQL-error class parity, and queryTags forwarding; feat(sea): wire rowLimit + statementConf + TIMESTAMP_NTZ/LTZ params #408 adds rowLimit, general statementConf, and TIMESTAMP_NTZ/LTZ params.
• Metadata methods are added in feat(sea): metadata methods — catalogs/schemas/tables/columns/functions/keys/typeInfo #404 and TLS connection options in feat(sea): expose TLS verification toggle + custom CA on ConnectionOptions #407.
• 2026-06-01 review-fix cascade: session defaults (initialCatalog, initialSchema, sessionConfig) are now passed on native openSession instead of the invalid second executeStatement argument, and the fix is carried through [SEA-NodeJS] (6/8) CloudFetch + Inline Arrow result fetching #381/[SEA-NodeJS] (7/8) Operation lifecycle — cancel / close / finished + INTERVAL parity + napi relocation #384/[SEA-NodeJS] (8/8) M1 Phase 1 — OAuth M2M + OAuth U2M (5 review rounds, ZERO HIGH at close) #383/feat(sea): expose maxConnections + lock complex types as Arrow default #392/feat(sea): queryTags through executeStatement + fetchAll regression lock #393/feat(sea): expose TLS verification toggle + custom CA on ConnectionOptions #407/feat(sea): wire rowLimit + statementConf + TIMESTAMP_NTZ/LTZ params #408.
• 2026-06-01 review-fix cascade: SEA session/operation ids now use native sessionId / statementId where available, and napi kernel-error decoding checks both reason and message without turning malformed envelopes into JSON parse errors.

Test plan

• ✅ M0 e2e at 535ms vs pecotesting
• ✅ runAsync polling internal to kernel; JS sees a sync-shaped promise
• ✅ openSession honors sessionConfig + initialCatalog + initialSchema

Draft until you give the go for review.

Tracking

• PECOBLR-2666 — NodeJS SEA integration (parent epic — core M0 executeStatement / openSession)

Co-authored-by: Isaac

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[gopalldb]

🔴 P0 (Critical) — verified at source, must fix

1. SeaOperationBackend.status() returns a Thrift-shaped object, not the neutral OperationStatus the contract requires — silently reports UNKNOWN for finished SEA statements.
   lib/sea/SeaOperationBackend.ts:176-180 (on origin/msrathore/sea-execution)

I confirmed the actual return:
public async status(_progress: boolean): Promise {
return { status: {...}, operationState: TOperationState.FINISHED_STATE } as TGetOperationStatusResp;
}
The contract requires Promise with a string .state field. The facade DBSQLOperation.status() feeds this to synthesizeThriftStatus, which reads status.state — but this object only has
.operationState. So status.state is undefined → operationStateToThrift(undefined) → default → UKNOWN_STATE. Every operation.status() on the SEA path reports UNKNOWN for a statement the kernel actually
finished.

The as TGetOperationStatusResp cast defeats tsc (which I separately confirmed passes clean on this stack) — so this is a silent runtime bug with no compiler safety net.
→ Fix: return { state: OperationState.Succeeded } (neutral DTO) and change the declared return type to Promise so the compiler can enforce it.

2. getResultMetadata() declared with the wrong type — primes the Arrow→column misroute activated in [SEA-NodeJS] (6/8) CloudFetch + Inline Arrow result fetching #381.
   lib/sea/SeaOperationBackend.ts:183-185

In #382 this method only throws ("lands in sea-results"), so zero runtime impact today — but it's declared Promise instead of the contract's Promise. That wrong
signature is exactly what let #381 fill it in returning resultFormat: TSparkRowSetType.ARROW_BASED_SET (a number), which resultFormatToThrift (switching on the string enum) silently maps to COLUMN_BASED_SET.
Fixing the declared type here would force #381 to build the correct neutral DTO and let tsc catch the mismatch.
→ Fix: declare Promise now, in the file that introduces it.

🟠 P1 (Important)

1. hasResultSet hard-coded true — SeaOperationBackend.ts:~456. The facade gates fetch/schema/hasMoreRows on this; for DDL/DML (SET/CREATE/INSERT) it'll drive fetch/schema paths instead of cleanly reporting
   "no result set." Masked today by stubbed fetch; the contract says implementations must refresh this from terminal status. → document the M0 result-bearing-only limitation or reject non-result statements.
2. rethrowKernelError never-typing + ! is load-bearing across 3 files — SeaBackend.ts, SeaSessionBackend.ts, SeaOperationBackend.ts. Correct today (it always throws), but the non-null assertions defeat the
   compiler if anyone ever makes a branch not throw. → add an invariant comment or restructure to return-in-try.

🟡 P2 (Minor)

• waitUntilReady() never throws on cancel/close — diverges from the contract (must throw OperationStateError on terminal non-success so the facade mirrors state). Low impact in M0.
• E2E doesn't exercise the read path — execution-e2e.test.ts asserts only operation.id is a string and close() doesn't throw; never calls status()/getMetadata()/reads a row. This is why the P0 lands green. A
  single await operation.status() asserting not-UNKNOWN would have caught it.
• Per-statement executeOptions forwarding may be a silent no-op against the merged binding — SeaSessionBackend.ts forwards executeOptions as a 2nd arg, but the merged kernel moved
  catalog/schema/sessionConfig to session-level openSession and executeStatement(sql) takes no options. Unit tests assert the driver sends it, not that the kernel applies it. Reconciled by [SEA-NodeJS] (6/8) CloudFetch + Inline Arrow result fetching #381 (which removes
  the forwarding) — a transient stack artifact, but if [SEA-NodeJS] (5/8) executeStatement + openSession (sessionConfig, initialCatalog/Schema) #382 shipped alone, initialCatalog/initialSchema/sessionConfig would silently not reach the kernel.

[msrathore-db]

Superseded — this layer is folded into the consolidated SEA foundation, now split into #409 → #410 → #411 (stacked on main).