tarunannapareddy opened a new issue, #17574: URL: https://github.com/apache/pulsar/issues/17574
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation **Email from Yunze Xu** Assuming users called "acknowledgeCumulative" periodically, there is a chance that some messages of the specific partition has never been passed to the method. For example, a consumer received: P0-M0, P1-M0, P0-M1, P1-M1, P0-M2, P1-M2... And the user acknowledged every two messages, i.e. P0-M0, P0-M1, P0-M2. Eventually, partition 1 has never been acknowledged. User must maintain its own `Map<String, MessageId>> cache for a partitioned topic or multi-topics consumer with the existing "acknowledgeCumulative" API. Should we make it more friendly for users? For example, we can make "acknowledgeCumulative" accept the map to remind users to maintain the map from topic name to message ID: **java** ``` // the key is the partitioned topic name like my-topic-partition-0 void acknowledgeCumulative(Map<String, MessageId> topicToMessageId); ``` ### Solution Implement acknowledgeCumulative(Map<String, MessageId> topicToMessageId) ### Alternatives _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- 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]
