Is your feature request related to a problem? Please describe.
Currently, the managed cursor maintains the acked messages by mark delete position and individual delete messages. All of the mark delete position and individual delete messages are faced to batch messages(ledgerId,entryId). For users, the single message is the publishing and consuming unit. Since the managed cursor can’t maintain the local index of a batch message, the broker will dispatch acked messages(not batch) to consumers like the issue #5969.
So, it's better to support for batch message local index acknowledgment. This issue tracks the task for this feature.
Is your feature request related to a problem? Please describe.
Currently, the managed cursor maintains the acked messages by mark delete position and individual delete messages. All of the mark delete position and individual delete messages are faced to batch messages(ledgerId,entryId). For users, the single message is the publishing and consuming unit. Since the managed cursor can’t maintain the local index of a batch message, the broker will dispatch acked messages(not batch) to consumers like the issue #5969.
So, it's better to support for batch message local index acknowledgment. This issue tracks the task for this feature.