Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stream Processing Error Handling Strategies #871

Open
emil14 opened this issue Feb 9, 2025 · 1 comment
Open

Stream Processing Error Handling Strategies #871

emil14 opened this issue Feb 9, 2025 · 1 comment
Assignees
Labels

Comments

@emil14
Copy link
Collaborator

emil14 commented Feb 9, 2025

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

@emil14 emil14 added the Critical label Feb 9, 2025
@emil14 emil14 self-assigned this Feb 9, 2025
@emil14
Copy link
Collaborator Author

emil14 commented Feb 9, 2025

Interrupt Processing (Fail Fast Weak)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant