flowchartsman commented on issue #183: URL: https://github.com/apache/pulsar-client-go/issues/183#issuecomment-940226846
I would like to chime in that there is a use-case this would be most useful: batch consumers. For example, if I want to make an every 6h/12h/24h report or bundle from a channel. To do this with a normal subscription, I would need to retain a potentially-unbounded set of messages (or at least message IDs) in memory to ack them all when complete. The other method (and the one I am currently using) is to use a reader, however this requires me to store my last offset in external state between job runs. With cumulative ack, I could accomplish this entirely within the pulsar ecosystem by simply resuming my subscription and then exiting the loop after an idle period or when I begin to receive messages within a certain small distance of job start time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
