Does cursor's deletedMessges track acked delayed messages after pip-195

[sammyne]

After enabling the bucket based delayed delivery tracker designed by pip-195, will cursor's deletedMessages still track the acked delayed messages, or just the acked non-delayed messages?

[Denovo1998]

After you switch to the bucket-based delayed delivery tracker (PIP-195), the subscription cursor’s deletedMessages / individuallyDeletedMessages still tracks all acked messages (including delayed ones), not only non-delayed messages.

[Denovo1998]

This may also be related to #25028.

[sammyne]

Regarding the Delayed Production proposed in #25028, curious of what message_id in CommandSendReceipt should be feedback to producer on successfully producing messages. @Denovo1998

[Denovo1998]

Here, after the client sends successfully, it needs to return the only traceable id in the external service.

[Denovo1998]

uniqDelayMsgId

https://github.com/didi/DDMQ/blob/master/carrera-common/src/main/java/com/xiaojukeji/carrera/chronos/model/InternalKey.java

[sammyne]

Here, after the client sends successfully, it needs to return the only traceable id in the external service.

Looking forward to more description to how this works~ I think the message_id field is a must for CommandSendReceipt.