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
Since 3.3.x, retryWhen(Function<Flux<Throwable>, Publisher>> is deprecated, and it is removed in 3.4.0-M2.
However, some users do still rely on reactor-extra 's reactor.retry.Retry builder, which implements Function rather than Retry.
The Retry.from(Function<Flux<RetrySignal>, Publisher>) utility method only helps halfway for a migration, because it is RetrySignal based and not Throwable based.
Desired solution
Adding a second utility adapter method, Retry.fromThrowable(Function<Flux<Throwable>, Publisher>), that performs the full adaptation.
Considered alternatives
A current way to adapt the code is to map the RetrySignal to its failure:
Motivation
Since 3.3.x,
retryWhen(Function<Flux<Throwable>, Publisher>>
is deprecated, and it is removed in 3.4.0-M2.However, some users do still rely on
reactor-extra
'sreactor.retry.Retry
builder, which implementsFunction
rather thanRetry
.The
Retry.from(Function<Flux<RetrySignal>, Publisher>)
utility method only helps halfway for a migration, because it isRetrySignal
based and notThrowable
based.Desired solution
Adding a second utility adapter method,
Retry.fromThrowable(Function<Flux<Throwable>, Publisher>)
, that performs the full adaptation.Considered alternatives
A current way to adapt the code is to map the
RetrySignal
to its failure:Additional context
See reactor/reactor-addons#231 for an example of an issue where users have trouble finding the correct migration path.
The text was updated successfully, but these errors were encountered: