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
{{ message }}
This repository was archived by the owner on Aug 30, 2026. It is now read-only.
Repository navigation
Commit 43ea4fa
Browse filesBrowse the repository at this point in the historyBrowse files
fix: allow zero durations to be set for connections (#3916)
SET statements that set a duration, e.g. max_commit_delay or statement_timeout,
did not allow setting a zero duration. This is however sometimes useful, as the
server default for max_commit_delay is not zero. This means that setting this to
zero triggers a different behavior than not setting a value, as when no value is
included in a commit request, Spanner will choose a reasonable value for the
commit delay. By explicitly setting it to zero, Spanner will always also use a
zero commit delay.
Copy file name to clipboardExpand all lines: google-cloud-spanner/src/main/java/com/google/cloud/spanner/connection/ClientSideStatementValueConverters.java
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -248,7 +248,8 @@ public Duration convert(String value) {
Copy file name to clipboardExpand all lines: google-cloud-spanner/src/main/java/com/google/cloud/spanner/connection/ConnectionStatementExecutorImpl.java
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -361,7 +361,7 @@ public StatementResult statementShowReturnCommitStats() {
0 commit comments