-
Notifications
You must be signed in to change notification settings - Fork 26.4k
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
[Survey] Is it necessary to continue to maintain zkclient in dubbo project? #3569
Comments
+1 to remove zkclient |
I think we can rely on curator directly as it has emerged as the facto standard of zk client tools. |
+1 Agreed to delete |
+1 remove |
+1 to remove |
I will remove it in dubbo-2.7.1 at this week.
If you have different opinions, please let me know as soon as possible.
kezhenxu94 <notifications@github.com> 于2019年2月28日周四 下午10:31写道:
… +1 to remove
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3569 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD5mbO8CG61O0G8HEVJNIdB5AettgA7lks5vR-hYgaJpZM4bRtPF>
.
--
Best Regard!
cvitory
|
I think we will remove zkclient firstly, but not to depend curator directly. This change is too big. |
There are two zookeeper implements that are curator and zkclient.
ZkClient github: https://github.com/sgroschupf/zkclient/tree/master/src/main/java/org/I0Itec/zkclient .
And the repository is not updated frequently.
So if you think we should continue to keep zkClient in dubbo project , please reply -1 and give us reason.
[+1] : remove.
[-1] :Keep. And give us some reason or what you encounter.
The text was updated successfully, but these errors were encountered: