-
Notifications
You must be signed in to change notification settings - Fork 46
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
bug: Return FORBIDDEN if a user's batch is Over Quota #848
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Wonderful 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was hoping we could take the opportunity to fix #418 here but I'm fine with a quicker fix such as this. This does not fix #418 though, so let's log a "propagate quota errors in batch commit" issue for this PR (I really should have logged it for my comment describing the issue ) and fixup the commit message to point to it
updated commit to reflect that this is an "issue" resolution to #418 rather than "closes" |
Issue #418
Description
If a user is over quota during a batch operation, the server would return OK with a list of
failed
ids. The client would retry them, leading to potentially a lot of useless network traffic.Testing
Enable the QUOTA system.
Create a batch that contains more data than should be allowed by the QUOTA.
Confirm that the returned result is a
403 FORBIDDEN
status with the body of14
(Note, I used the spanner load test script for this.)
Issue(s)
Issue #418