Skip to content
This repository has been archived by the owner on Apr 1, 2024. It is now read-only.

ISSUE-5752: Expose key shared consumer selector range in API #160

Closed
sijie opened this issue Dec 27, 2019 · 0 comments
Closed

ISSUE-5752: Expose key shared consumer selector range in API #160

sijie opened this issue Dec 27, 2019 · 0 comments
Labels
component/stats help wanted Extra attention is needed triage/week-47 type/feature workflow::triaged

Comments

@sijie
Copy link
Member

sijie commented Dec 27, 2019

Original Issue: apache#5752

Is your feature request related to a problem? Please describe.
When using Key-Shared subscription, there's currently no way to know which consumer will read a given message based on its key.

Describe the solution you'd like
It would be nice if the selector range handled by a consumer is exposed in the relevant subscription stats API/endpoints.
For instance in /{topic}/stats.

Related to #4077 #4079 #4169
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
component/stats help wanted Extra attention is needed triage/week-47 type/feature workflow::triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sijie @MarvinCai