Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] Use clientDecode for consuming message directly #7676

Closed
1 task done
cserwen opened this issue Dec 19, 2023 · 0 comments · Fixed by #7677
Closed
1 task done

[Enhancement] Use clientDecode for consuming message directly #7676

cserwen opened this issue Dec 19, 2023 · 0 comments · Fixed by #7677

Comments

@cserwen
Copy link
Member

cserwen commented Dec 19, 2023

Before Creating the Enhancement Request

  • 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,
image

Describe Alternatives You've Considered

No

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant