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.

Sign up for GitHub

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

Jump to bottom

Support specify dispatch policy for the non-key message in Key_Shared subscription mode #6553

Open
codelipenghui opened this issue Mar 19, 2020 · 1 comment
Open

Support specify dispatch policy for the non-key message in Key_Shared subscription mode #6553

codelipenghui opened this issue Mar 19, 2020 · 1 comment
Labels
area/broker lifecycle/stale type/feature The PR added a new feature or issue requested a new feature

Comments

@codelipenghui
Copy link
Contributor

codelipenghui commented Mar 19, 2020 •
edited
Loading

Master issue: #4077
Is your feature request related to a problem? Please describe.
Currently, the non-key message dispatch to a consumer in Key_Shared subscription mode. It's better to support set up the dispatch policy at the client-side.

Describe the solution you'd like
Allow the client to set up a non-key message dispatch policy.
@codelipenghui codelipenghui added the type/feature The PR added a new feature or issue requested a new feature label Mar 19, 2020
@codelipenghui codelipenghui mentioned this issue Mar 19, 2020
Closed
12 tasks
@sijie sijie mentioned this issue Mar 19, 2020
Open
@lhotari
Copy link
Member

lhotari commented Oct 4, 2024

Not exactly implementing a dispatch policy, but #23219 addresses non-key entries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/broker lifecycle/stale type/feature The PR added a new feature or issue requested a new feature
Projects
Apache Pulsar / Key_Shared and Acknowledgement reliability and usability improvements
Status: No status
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lhotari @sijie @codelipenghui @tisonkun