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
Is your feature request related to a problem? Please describe.
I have some finish logic running when all currently pushed data has been processed (some stats update and external backpressure). Right now I use idle timeout (wait some minutes, and if no messages received, conclude topic end has been reached). But it is a very fragile way.
Describe the solution you'd like
It would be much better to have some (instrumentation?) event fired when consumer reaches end of topic (for all partitions simultaneously).
The text was updated successfully, but these errors were encountered:
Hi @SergeyFromHell, you can implement this feature without new code. You can listen to the END_BATCH_PROCESS instrumentation event and compare the highWatermark with your current offset, if they are off by one you can emit an event saying that you reached the end of the topic. To cater to all partitions you will have to keep some state, but it's also possible.
Is your feature request related to a problem? Please describe.
I have some finish logic running when all currently pushed data has been processed (some stats update and external backpressure). Right now I use idle timeout (wait some minutes, and if no messages received, conclude topic end has been reached). But it is a very fragile way.
Describe the solution you'd like
It would be much better to have some (instrumentation?) event fired when consumer reaches end of topic (for all partitions simultaneously).
The text was updated successfully, but these errors were encountered: