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

Expose key shared consumer selector range in API #5752

Closed
cbornet opened this issue Nov 26, 2019 · 1 comment · Fixed by #8567
Closed

Expose key shared consumer selector range in API #5752

cbornet opened this issue Nov 26, 2019 · 1 comment · Fixed by #8567
Labels
help wanted type/feature The PR added a new feature or issue requested a new feature

Comments

@cbornet
Copy link
Contributor

cbornet commented Nov 26, 2019

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

@cbornet cbornet added the type/feature The PR added a new feature or issue requested a new feature label Nov 26, 2019
@jiazhai
Copy link
Member

jiazhai commented Nov 27, 2019

Thanks @cbornet for watching on this. will put this in our backlog. It would be great if you or any other would like to contribute to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted type/feature The PR added a new feature or issue requested a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants