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
Address review: reuse one fallback KernelBackend, guard cause overwrite
- ThriftBackend: reuse a single fallback KernelBackend across all Reyden (KP001)
fallback sessions on the connection instead of constructing one per openSession.
connectionOptions are fixed after connect, so it is created + connected once
(lazily, memoized; the attempt is cleared on connect failure so a later open can
retry) and released in close() — this stops per-session accumulation of backends
and process-global log-bridge listeners.
- On the double-failure path, only set the kernel error's `cause` when it is absent,
so a cause the kernel error may already carry is not clobbered.
- Test now opens two fallback sessions and asserts a single KernelBackend is created
and connected once, reused for both, and closed once on close().
Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Rahul Singhal <rahul.singhal@databricks.com>
0 commit comments