-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Prototype: Composable retry classifiers - enable composition in Azure.Core #41542
Prototype: Composable retry classifiers - enable composition in Azure.Core #41542
Conversation
context.AddClassifier(404, false); | ||
context.AddClassifier(500, false); | ||
context.AddClassifier(new RetryClassificationHandler()); | ||
context.AddClassifier(new StatusCodeHandler(404, true)); |
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.
Illustrates how an end-user would compose retriable-response and error-response classifiers using handler approach. Note that adding a handler via this interface means that we must use a ChainingClassifier for both retry and error classifications. This adds performance overhead to the optimized StatusCodeClassifier for when classifying errors for all calls to pipeline.Send for this operation.
An implementation that lets users customize retry classification without impacting error classification performance might be preferable.
API change check APIView has identified API level changes in this PR and created following API reviews. |
…clientmodel-compose-retryclassifiers
…clientmodel-compose-retryclassifiers
Closing in favor of #41595 |
Investigation into issue #41465