spanner: support automatic Session refreshes#406
Draft
cliff-openai wants to merge 1 commit intoyoshidan:mainfrom
Draft
spanner: support automatic Session refreshes#406cliff-openai wants to merge 1 commit intoyoshidan:mainfrom
cliff-openai wants to merge 1 commit intoyoshidan:mainfrom
Conversation
Without this PR, in cases where Cloud Spanner "forgets" a session (which does not happen often, but does happen), clients could see persistent errors along the lines of: `status: 'Some requested entity was not found', self: \"Session not found: (session_id)\"`. This change implements automatic session refresh in these cases. It is very heavily inspired by the way that the Cloud Spanner golang client handles these errors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Without this PR, in cases where Cloud Spanner "forgets" a session (which does not happen often, but does happen), clients could see persistent errors along the lines of:
status: 'Some requested entity was not found', self: \"Session not found: (session_id)\".This change implements automatic session refresh in these cases. It is very heavily inspired by the way that the Cloud Spanner golang client handles these errors.
This PR is currently in Draft because I have not done enough testing yet, but I'm happy to take early feedback