-
Notifications
You must be signed in to change notification settings - Fork 68
chore: move the attemptFailed
logic from BaseApiTracer to ApiTracer
#3037
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
Conversation
attemptFailed
overload logic from BaseApiTracer to ApiTracer
attemptFailed
overload logic from BaseApiTracer to ApiTracerattemptFailed
logic from BaseApiTracer to ApiTracer
@@ -121,7 +123,10 @@ default Scope inScope() { | |||
* @param error the transient error that caused the attempt to fail. | |||
* @param delay the amount of time to wait before the next attempt will start. | |||
*/ | |||
default void attemptFailedDuration(Throwable error, java.time.Duration delay) {}; | |||
default void attemptFailedDuration(Throwable error, java.time.Duration delay) { | |||
// defaults to do the same as attemptFailed(Throwable, org.threeten.bp.Duration) |
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.
nit: Can you add a blurb to reflect the why
?
i.e. Customers may have older/legacy code that directly implements ApiTracer's attemptFailed()
method and their overriden logic should be invoked in gax.
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.
Good suggestion, thank you. I added a similar blurb in the body comment.
|
|
Follow up of #3016
On


bigtable
andspanner
:Thanks @blakeli0 and @lqiu96 for the directions.