-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add consumer_limits
and first_seq
to Stream Config
#242
Comments
@neilalexander maybe you can explain the behaviour of these for us, it says:
But also these are limits? So are they maximums or defaults or both a default and a maximum? I want to be sure to get the description in the schemas right |
I added some explanations based on our discussions. |
I've talked directly to Neil and Tomasz. There is some clarity to be gained on the explanation of consumer limits, but I don't think there is anything for the client to do, the server will return an error if there is a constraint violation when updating a stream of adding/updating a consumer. |
Overview
Two additional fields were added in 2.10:
consumer_limits
first_seq
consumer_limits
A new field in
StreamConfig
that is a struct representing consumer limits created on given stream.inactive_threshold
ormax_ack_pending
, those will be left as they are. If passed value is too high (above limits), consumer creation will fail. Stream will not lower those values.first_seq
Defines sequence from which stream starts when created
Not documented in ADRs.
Not mandatory for 2.10 client release if causes release delay.
Clients and Tools
Other Tasks
Implemented
Client authors please update with your progress. If you open issues in your own repositories as a result of this request, please link them to this one by pasting the issue URL in a comment or main issue description.
The text was updated successfully, but these errors were encountered: