spanner: client library doesn’t handle a non-existent session error in all places #6422
Description
We think that if the backend has closed the session, then the client is meant to create a new session and pass that to the user instead of letting this exception bubble up to the user.
WARNING: Error during call to readRow. [CONTEXT ratelimit_period="1 MINUTES" ]
com.google.cloud.spanner.SpannerException: NOT_FOUND: io.grpc.StatusRuntimeException: NOT_FOUND: Session not found: projects/<project>/instances/<instance>/databases/<database>/sessions/<session id>
resource_type: "type.googleapis.com/google.spanner.v1.Session"
resource_name: "projects/<project>/instances/<instance>/databases/<database>/sessions/<session id>"
description: "Session does not exist."