=str #22917 recoverWithRetries allow 0 and negative values
This commit is contained in:
parent
ee79a3d1a8
commit
b7d7316c1c
9 changed files with 51 additions and 16 deletions
|
|
@ -939,7 +939,7 @@ Throwing an exception inside `recoverWith` _will_ be logged on ERROR level autom
|
|||
RecoverWithRetries allows to switch to alternative Source on flow failure. It will stay in effect after
|
||||
a failure has been recovered up to *attempts* number of times so that each time there is a failure
|
||||
it is fed into the *pf* and a new Source may be materialized. Note that if you pass in 0, this won't
|
||||
attempt to recover at all. Passing -1 will behave exactly the same as *recoverWith*.
|
||||
attempt to recover at all. A negative `attempts` number is interpreted as "infinite", which results in the exact same behavior as `recoverWith`.
|
||||
|
||||
Since the underlying failure signal onError arrives out-of-band, it might jump over existing elements.
|
||||
This stage can recover the failure signal, but not the skipped elements, which will be dropped.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue