You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@helix.apache.org by GitBox <gi...@apache.org> on 2019/10/30 19:19:27 UTC
[GitHub] [helix] kaisun2000 opened a new issue #556: Move Zookeeper Access
Layer into separate module
kaisun2000 opened a new issue #556: Move Zookeeper Access Layer into separate module
URL: https://github.com/apache/helix/issues/556
We need consolidate the Zookeeper accessing code into a separate module, helix-zk. This would pave the way to further scaling Zookeeper horizontally
The intended class and interfaces to be moved are the following:
HelixZkClient
HelixZkClientFactory
DedicatedZkClientFactory
SharedZkClientFactory
ZkConnectionManager
zookeeper/ZkClient
zookeeper/ZkConnection
zookeeper/ZkEventThread
PathBasedZkSerializer
BasicZkSerializer
ChainedPathZkSerializer
PreFetch
ZkAsyncCallbacks
ZkClient
The goal is to make it backward compatible. Namely users of the helix-core would not need to change code that they would still be able to compile the code and maintain the same behavior
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For additional commands, e-mail: reviews-help@helix.apache.org