Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: remove the statement of session number limits #1928

Merged
merged 6 commits into from
Nov 18, 2022
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,10 @@
* 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.
*
* <p>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}.
* <p>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}.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rbrtwng : Please remove the whitespace at the end of this line, its failing one of the required presubmits for linting.

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