You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that after using ReconsumeLaterAsync, the messages that originally had a value for the key have an empty key when consumed again.
I found that the issue is mainly in the function getOptionalKey in the file src\Pulsar.Client\Internal\DeadLetters.fs. This function only sets the PartitionKey when message.Key is empty.
let getOptionalKey (message: Message<'T>) =
if String.IsNullOrEmpty(%message.Key) then
Some { PartitionKey = message.Key; IsBase64Encoded = message.HasBase64EncodedKey }
else
None
The text was updated successfully, but these errors were encountered:
I noticed that after using ReconsumeLaterAsync, the messages that originally had a value for the key have an empty key when consumed again.
I found that the issue is mainly in the function getOptionalKey in the file src\Pulsar.Client\Internal\DeadLetters.fs. This function only sets the PartitionKey when message.Key is empty.
The text was updated successfully, but these errors were encountered: