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
This issue is likely the same for individual stream subscriptions, but it isn't clear how to determine when a subscriber is caught up.
One use case: Running a batch job to create a read model, or a new stream.
It is currently not clear how to tell when subscription is caught up and the batch process can end. We're using allStream subscriptions with filters because it is a large database and all we want are the relevant events.
Currently the API delivers: 'data', 'close', 'confirmation', 'end', 'error', 'readable'.
Is the expectation that the 'readable' event get used for this?
The text was updated successfully, but these errors were encountered:
This issue is likely the same for individual stream subscriptions, but it isn't clear how to determine when a subscriber is caught up.
One use case: Running a batch job to create a read model, or a new stream.
It is currently not clear how to tell when subscription is caught up and the batch process can end. We're using allStream subscriptions with filters because it is a large database and all we want are the relevant events.
Currently the API delivers: 'data', 'close', 'confirmation', 'end', 'error', 'readable'.
Is the expectation that the 'readable' event get used for this?
The text was updated successfully, but these errors were encountered: