[fix][client] Fix deserialized BatchMessageIdImpl acknowledgment failure #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes apache#19030
Motivation
When a
BatchMessageIdImpl
is created from a deserialization, theBatchMessageAcker
object cannot be shared by all instances in the same batch, which leads to an acknowledgment failure when batch index ACK is disabled (by default).Modifications
Maintain a map from the
(ledger id, entry id)
pair to theBatchMessageAcker
inConsumerImpl
. If theBatchMessageIdImpl
doesn't carry a validBatchMessageAcker
, create and cache aBatchMessageAcker
instance and remove it when all messages in the batch are acknowledged.It requires a change in
MessageIdImpl#fromByteArray
that aBatchMessageAckerDisabled
will be created to indicate there is no shared acker.To avoid making code more complicated, this patch refactors the existing code that many logics about consumer are moved from the ACK tracker to the consumer. It also removes the
AckType
parameter when acknowledging a list of messages.