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 have confirmed that this should be classified as an enhancement rather than a bug/feature.
Summary
Currently, when users push messages directly from the console, messageExt.getMsgId returns offsetMsgID instead of the uniqId generated by the client, which may cause confusion for users.
Motivation
In order to make the msgID seen by production and consumption consistent
Describe the Solution You'd Like
Use clientDecode method instead of decode,
Describe Alternatives You've Considered
No
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Enhancement Request
Summary
Currently, when users push messages directly from the console, messageExt.getMsgId returns offsetMsgID instead of the uniqId generated by the client, which may cause confusion for users.
Motivation
In order to make the msgID seen by production and consumption consistent
Describe the Solution You'd Like
Use clientDecode method instead of decode,
Describe Alternatives You've Considered
No
Additional Context
No response
The text was updated successfully, but these errors were encountered: