apache / apache/pulsar

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

Open
#6,553 1 comment 0 reactions 0 assignees View on GitHub
area/broker lifecycle/stale type/feature
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 22h
Merged PRs (30d)
142

Description

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.

Contributor guide

Open the contributing guide

Research direction

Start with master issue #4077 and the Key_Shared subscription behavior described here; no source file or test is named in the issue. Clarify the supported non-key message dispatch policies and the client-side configuration surface, then define completion through tests covering the selected policy.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.