Hi @pppp
Good day!!
The JavaScript SDK session object (what you get from client.openSession()) can expire if unused or idle for a certain period. This behavior was noted explicitly in the related GitHub discussion:
after some period of inactivity the session will expire and you’ll start getting errors.
However:
-
Databricks does not currently provide a documented configuration to change the idle timeout for SQL sessions used via the SDK.
-
There’s no SQL parameter like idle_session_timeout exposed for Databricks SQL sessions (unlike some databases). The only timeout parameter documented is STATEMENT_TIMEOUT, which is about execution duration, not session inactivity.
-
The server will drop sessions after inactivity but the exact timeout value isn’t publicly documented like the SQL timeout is.
Kindly let me know if you have any questions on this.