-
Notifications
You must be signed in to change notification settings - Fork 542
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 zookeeper chroots #2
Comments
Correct. I'm planning to upgrade Secor to kafka 0.81 that has an API for updating consumer offsets. Consequently, Secor won't be directly modifying zk's nodes. |
cool, would also be good to configure the /secor/locks path prefix |
Good point. |
Minor updates to the design doc
What was the result for this? Can the chroot be specified somehow? For example we configure the broker to use /kafka. I don't see how to configure that other than append to the zookeeper.quarum. But looking at
|
Ok, sorry. I see its available in config/secor.common.properties. |
More unit tests, ensure Avro schemas update, bug fix in ProtobufUtil
Upgrade aws-java-sdk-s3 1.11.118 -> 1.11.119
* Add FormatConvertingUploadManager * [DP-313] Dont drop messages on rebalance * Address PR feedback * Remove some println's
Fixed a bug in remote url and path.
secor currently assumes kafka is pointed at the root zk node
The text was updated successfully, but these errors were encountered: