From ddd062527674659ca2ea73e079bca4dee62ca67f Mon Sep 17 00:00:00 2001 From: Robert Wang Date: Thu, 17 Nov 2022 20:14:14 -0800 Subject: [PATCH] fix: remove the statement of session number limits (#1928) Cloud Spanner no longer has the 10K "Sessions per database per node" limit. Doc fix only Fixes #1927 --- .../src/main/java/com/google/cloud/spanner/Session.java | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/google-cloud-spanner/src/main/java/com/google/cloud/spanner/Session.java b/google-cloud-spanner/src/main/java/com/google/cloud/spanner/Session.java index 697521554e..d322e0fb6d 100644 --- a/google-cloud-spanner/src/main/java/com/google/cloud/spanner/Session.java +++ b/google-cloud-spanner/src/main/java/com/google/cloud/spanner/Session.java @@ -28,10 +28,9 @@ * read-write/write-only transactions, create multiple sessions. Note that standalone reads and * queries use a transaction internally, and count toward the one transaction limit. * - *

Cloud Spanner limits the number of sessions that can exist at any given time; thus, it is a - * good idea to delete idle and/or unneeded sessions. Aside from explicit deletes, Cloud Spanner can - * delete sessions for which no operations are sent for more than an hour, or due to internal - * errors. If a session is deleted, requests to it return {@link ErrorCode#NOT_FOUND}. + *

It is a good idea to delete idle and/or unneeded sessions. Aside from explicit deletes, Cloud + * Spanner can delete sessions for which no operations are sent for more than an hour, or due to + * internal errors. If a session is deleted, requests to it return {@link ErrorCode#NOT_FOUND}. * *

Idle sessions can be kept alive by sending a trivial SQL query periodically, for example, * {@code SELECT 1}.