-
Notifications
You must be signed in to change notification settings - Fork 737
Feat tmv2 audit #3249
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
Feat tmv2 audit #3249
Conversation
| if err != nil { | ||
| d.setErr(fmt.Errorf("error when heading info of object %s: %v", data.key, err)) | ||
| } else { | ||
| d.incrObjectsFailed(1) |
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.
above you mention about object failed
this value might not be the real number of failure if user passed a customized failure policy
but couldn't we just still increment the count of objects failed, even if the user passes a custom policy?
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 mean it depends on how we define this field and how user implements the policy. If user policy retried the request and succeeded, they might not consider that object as a failed count
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.
You're right, thinking more about it, it's only if the retry policy also returns an error that this counts as failed.
However, I still think that we have an accurate count of failed get/uploads
- If user provides standard policies, we are counting correctly
- If user provides their own policies, and they successfully/unsuccessfully retry, we would still know whether it was successful or not depending on whether they return
error not
f2aee8a to
2bbe6ef
Compare
2bbe6ef to
8c6ee20
Compare
Update remaining features to transfer manager v2 according to latest SEP specification: