-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Support kafka 3.0 topics #337
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.
Hello and thank you for the PR!
Take a look at the inline comments.
Regarding dropping the zookeeper
option:
Given that ZooKeeper and bootstrap server are two different subsystems I suggest that we keep both of the options for now. Also, some versions of Kafka that can use zookeeper
option are not yet EoL (e.g 2.4.x).
To have one of the two options defined i think it can be achieved with:
if !$zookeeper && !$bootstrap_server {
fail('Either zookeeper or bootstrap_server parameter must be defined!')
}
Thanks for the quick replies! I added all the changes, looks better now 🙂 |
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.
Please squash your commits before merging 😄
Done! |
Thanks for merging and your support! |
Pull Request (PR) description
In kafka 3.0 the
--zookeeper
option was removed for topics. It was deprecated in v2.2.0 (March 2019) and--bootstrap-server
has been available since then. I'm unsure if we should replacezookeeper
withbootstrap-server
completely or allow both options, but in that case I don't know how to require at least one of both arguments. Open for discussion here.This Pull Request (PR) fixes the following issues
Fixes #302