RobertIndie commented on issue #183: URL: https://github.com/apache/pulsar-client-go/issues/183#issuecomment-1340536526
Hi @Gleiphir2769 , Thanks for bringing this up. Overall, I'm +1 for implementing this feature. > But in the go client, only one message will be acknowledged per acknowledgment request. Which means cumulative ack will save the ack rpc times. Right, supporting the cumulative ack will also improve the performance. But We could also implement the ack group tracker to aggregate serval ack(individual or cumulative) into one RPC. This could improve the performance of the individual ack. > For example, a user need to consume 10000 messages continuously. The user may discard all previous messages because the 8000th message is wrong. In this scenario, if cumulative ack is introduced, the user can call cumulative ack directly with the 8000th message and start to receive new message sequence. Caching message ids here I don't think is a good idea. This case makes sense to me. +1 for implementing this feature. -- 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]
