-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Document retry of exceptions while streaming 'read'/'execute_sql' results #3790
Document retry of exceptions while streaming 'read'/'execute_sql' results #3790
Conversation
print row | ||
except Exception: | ||
result = snapshot.read( | ||
table, columns, keys, resume_token=result.resume_token) |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
@vkedia The |
Yes but each successful fetch might not have a resume_token. Also the StreamedResultSet returns the resume_token from the last PRS to the user even though the PRS itself might not have been yielded to the user since it does not form a complete row yet. That will lead to problem 2 I mentioned. |
See: #3775.
This PR does not close that issue: it only documents the actual, current retry semantics, instead of the intended-but-not-yet-implemented semantics in the current docs.