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

sijie · 2020-03-19T03:07:07Z

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.

The text was updated successfully, but these errors were encountered:

sijie added the type/feature label Mar 19, 2020

sijie added component/broker triage/week-13 labels Mar 26, 2020

sijie added the workflow::backlog label Apr 9, 2020

codelipenghui self-assigned this Apr 20, 2020

sijie unassigned codelipenghui Sep 4, 2020

sijie added the Stale label Mar 4, 2022

sijie mentioned this issue Jan 14, 2020

ISSUE-5438: Test errors in DispatcherBlockConsumerTest #396

Open

sijie added the scope/broker label Mar 11, 2022

sijie added the lifecycle/stale label May 27, 2022

sijie removed the triage/week-13 label Nov 21, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

sijie commented Mar 19, 2020

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

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

Comments

sijie commented Mar 19, 2020