You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Unable to know with the response in failover library whether its a real server exception or a client exception
Describe the solution you'd like
It would be nice to parameterize the exceptions that failover library can consider like 5xx exceptions and exclude others. May be dependes on the consumers of the library to choose what exceptions they want to handle as part of failover.
Describe alternatives you've considered
As a tactical, we can also provide a status code of the exception in the response so that client can decide what they want to do with a specific exception.
Which module is impacted
The impacted modules are :
failover-domain
[x ] failover-core
failover-store-inmemory
failover-store-caffeine
failover-store-jdbc
failover-store-async
failover-aspect
failover-scheduler
failover-lookup
failover-execution-resilience
failover-spring-boot-autoconfigure
failover-spring-boot-starter
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Unable to know with the response in failover library whether its a real server exception or a client exception
Describe the solution you'd like
It would be nice to parameterize the exceptions that failover library can consider like 5xx exceptions and exclude others. May be dependes on the consumers of the library to choose what exceptions they want to handle as part of failover.
Describe alternatives you've considered
As a tactical, we can also provide a status code of the exception in the response so that client can decide what they want to do with a specific exception.
Which module is impacted
The impacted modules are :
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: