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
Interestingly we might need onErrorContinue on Mono since Flux operations themselves produce Mono (collect, next..).
I was discussing with a user who did use an API (CF Java Client) that internally was operating a flux and returned to the user a collected view. Unfortunately the CF Java Client map operation used was producing rare NPE and the user wanted to filter these anomalies instead of fully retrying or interrupting the flow. Since the user had a mono he did workaround this way:
Interestingly we might need onErrorContinue on Mono since Flux operations themselves produce Mono (collect, next..).
I was discussing with a user who did use an API (CF Java Client) that internally was operating a flux and returned to the user a collected view. Unfortunately the CF Java Client map operation used was producing rare NPE and the user wanted to filter these anomalies instead of fully retrying or interrupting the flow. Since the user had a mono he did workaround this way:
The text was updated successfully, but these errors were encountered: