-
Notifications
You must be signed in to change notification settings - Fork 515
feat: support subscribeMode field on pulsar #3831
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Eric Shen <ericshenyuhao@outlook.com>
Signed-off-by: Eric Shen <ericshenyuhao@outlook.com>
…ulsar-subscription-mode
@ericsyh - Is there an issue number for this PR? |
@msfussell sorry i missed the issue create before, just created a new issue of #3832 and linked on this PR. |
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
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.
Looking good to me, just a few nits
} | ||
} | ||
|
||
func getSubscriptionMode(subsModeStr string) pulsar.SubscriptionMode { |
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.
I would like to see the addition of tests for this function to ensure future changes don't cause regressions
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.
Co-authored-by: Mike Nguyen <hey@mike.ee> Signed-off-by: Eric Shen <ericshenyuhao@outlook.com>
Signed-off-by: Eric Shen <ericshenyuhao@outlook.com>
@nelson-parente @mikeee Could you help review again? cc @yaron2 @JoshVanL help review |
Description
Please explain the changes you've made
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #3832
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: