This feature is about implementing a mechanism to handle inactive transactions to prevent session leaks.
Reference (java-spanner & go-sql-spanner):
Both libraries provide this feature as a client-side option (InactiveTransactionRemovalOptions or SessionPoolOptions). It allows for warning on or automatically closing transactions that have been idle for a certain period.
Implementation suggestion for spanner-mycli:
This could be implemented as a session-init-only system variable, e.g., CLI_INACTIVE_TRANSACTION_ACTION, which could take values like 'WARN' or 'WARN_AND_CLOSE'. This variable would be used during client initialization to configure the session pool behavior.
This feature is about implementing a mechanism to handle inactive transactions to prevent session leaks.
Reference (
java-spanner&go-sql-spanner):Both libraries provide this feature as a client-side option (
InactiveTransactionRemovalOptionsorSessionPoolOptions). It allows for warning on or automatically closing transactions that have been idle for a certain period.Implementation suggestion for
spanner-mycli:This could be implemented as a session-init-only system variable, e.g.,
CLI_INACTIVE_TRANSACTION_ACTION, which could take values like'WARN'or'WARN_AND_CLOSE'. This variable would be used during client initialization to configure the session pool behavior.