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
There are 3 possible error-handling strategies and none of them are supported at the moment.
Skip and Continue (Best Effort)
If error occur, propagate it downstream and process next element. Will be covered by #861
Interrupt Processing (Fail Fast Weak)
If error occur, propagate it downstream, close the output stream and wait for closing input stream, skipping next elements.
Interrupt Producing (Fail Fast Strong)
If error occur, propagate it downstream, close the output stream and send signal to stream-producer, that stream generation must be stoped, and wait for the closing of the input stream. Will be covered by #666
The text was updated successfully, but these errors were encountered:
If "fail fast strong" is supported chances are we don't need weak version. Let's implement that first and see how convenient that'll be.
The main point of this issue, maybe, is to stress that "fail fast weak" should not be default error handling strategy for stream-processors, otherwise "best effort" won't be supported
Problem
There are 3 possible error-handling strategies and none of them are supported at the moment.
Skip and Continue (Best Effort)
If error occur, propagate it downstream and process next element. Will be covered by #861
Interrupt Processing (Fail Fast Weak)
If error occur, propagate it downstream, close the output stream and wait for closing input stream, skipping next elements.
Interrupt Producing (Fail Fast Strong)
If error occur, propagate it downstream, close the output stream and send signal to stream-producer, that stream generation must be stoped, and wait for the closing of the input stream. Will be covered by #666
The text was updated successfully, but these errors were encountered: