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.

Sign up for GitHub

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

Jump to bottom

feat: mark when a Spanner client is closed #198

Merged
merged 1 commit into from May 14, 2020
Merged

feat: mark when a Spanner client is closed #198

merged 1 commit into from May 14, 2020

Commits on May 12, 2020

  1. feat: mark when a Spanner client is closed 

    Closing a Spanner client means that all resources that have been returned
by the client are no longer valid, including all DatabaseClients and
corresponding session pools. This will cause errors for any other process
that might still want to use these resources. This change marks when and by
which call stack a Spanner client is closed, and includes that in any
subsequent IllegalStateException that is returned to any process that tries
to use the resources that have been returned by the Spanner client. This
makes it easier to track down where and when a Spanner client is closed by
accident.
    @olavloite
    olavloite committed May 12, 2020
    Copy the full SHA
    01f7e04 View commit details
    Browse the repository at this point in the history