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, if exception is thrown from callback, we flush partial batch and continue.
This does not have clear semantics on what happens next (i.e. whoever runs such batch may close container, but likely he/she will not).
Even if container is closed, we still push partial batch out.
I think this is wrong and we should close container, similar how we do with any exception during op processing (DataCorruptionError, CreateProcessingError usages)
The text was updated successfully, but these errors were encountered:
Today, if exception is thrown from callback, we flush partial batch and continue.
This does not have clear semantics on what happens next (i.e. whoever runs such batch may close container, but likely he/she will not).
Even if container is closed, we still push partial batch out.
I think this is wrong and we should close container, similar how we do with any exception during op processing (DataCorruptionError, CreateProcessingError usages)
The text was updated successfully, but these errors were encountered: