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
Today, we have to have at least a Source and a Sink. This means we need to write the message from the Source vertex to the ISB so that the Sink vertex can pick it up. For simple processing needs, one could avoid having the ISB altogether and implement Source and Sink in the same Vertex. SourcerSinker cannot support exactly-once semantics if the source does not support it because the Ack will be done after the message has been written on Sink, and we can hit the 2-generals problem.
Use Cases
If you are okay with the at-least-once semantics and want to avoid the cost of writing to ISB when the processing function is cheap to execute.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The content you are editing has changed. Please copy your edits and refresh the page.
Summary
Today, we have to have at least a Source and a Sink. This means we need to write the message from the Source vertex to the ISB so that the Sink vertex can pick it up. For simple processing needs, one could avoid having the ISB altogether and implement Source and Sink in the same Vertex. SourcerSinker cannot support exactly-once semantics if the source does not support it because the Ack will be done after the message has been written on Sink, and we can hit the 2-generals problem.
Use Cases
If you are okay with the at-least-once semantics and want to avoid the cost of writing to ISB when the processing function is cheap to execute.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
Tasks
The text was updated successfully, but these errors were encountered: