-
Notifications
You must be signed in to change notification settings - Fork 622
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
CASSGO-28 ignore error retry type #1811
base: trunk
Are you sure you want to change the base?
Conversation
Can you add a test to ensure that the issue is actually fixed? And to prevent regressions. |
Hello! OK I will try to get to it on this weekend |
68ccfd0
to
5a5bf22
Compare
Added a test. Wanted to let observer know that error was ignored but observer is called before retry policy is checked. there is one more problem - error will not be ignored if we have no more attempts. Added a fix&test for this too |
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.
Looks good. +1 assuming CI passes.
Please format your commit message following the rules stated in CONTRIBUTING.md and add this JIRA to the CHANGELOG.md
in the Fixed
section of Unreleased
, thanks!
If you can't squash and rewrite the commit message the committer will do it for you when the PR is merged.
We need another committer +1 to merge this.
RetryType Ignore is documented and should work according to the documentation. Error is not returned to caller on ignore but can be seen in ObservedQuery. RetryType should be checked even if RetryPolicy.Attempt returns false, otherwise Ignore will not work on last attempt. Patch by Rikkuru; reviewed by João Reis for CASSGO-28
You mean anyone who've made a commit or apache employee ? |
Committers are people who have write access to the codebase, a PR needs two +1s from committers to get merged ideally and I'm a committer so we need one more. |
Closes #1808