-
Notifications
You must be signed in to change notification settings - Fork 664
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
[CHANGED] Simplified JetStream API changes and improvements #1300
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but before LGTM:
Are we 100% sure, that in few months, we will not regret not having context in publish async? :)
@Jarema I don't think so since we are not waiting for response from the server in the method itself, so really there is nothing to be canceled here. |
IIRC we could block PublishAsync based on the outstanding ack window. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Piotr Piotrowski <piotr@synadia.com>
Signed-off-by: Piotr Piotrowski <piotr@synadia.com>
Signed-off-by: Piotr Piotrowski <piotr@synadia.com>
Signed-off-by: Piotr Piotrowski <piotr@synadia.com>
270c2d1
to
bfe9100
Compare
PullThresholdBytes
optionConsumerConfig
context.Context
fromPublishAsync
andPublishMsgAsync
AddConsumer
toCreateOrUpdateConsumer
- this change is introduced in anticipation for separation of create and update operations in nats-server. After they'll be introduced, there will be 3 methods:CreateOrUpdateConsumer()
- current upsert behaviorCreateConsumer()
- will not overwrite consumerUpdateConsumer()
- will fail if consumer does not exist