GitHub user Randgalt opened a pull request:
https://github.com/apache/zookeeper/pull/122
[ZOOKEEPER-2642] Resurrect the reconfig() methods that were in
ZooKeeper.java.
Resurrect the reconfig() methods that were in ZooKeeper.java. While 3.5.x
is an alpha there are clients in production that are relying on the current
specification. The reconfig() methods are marked deprecated to inform that they
will be removed later. The "new" methods in the new class ZooKeeperAdmin were
renamed reconfigure() to avoid getting the deprecation annotation inherited and
to provide clarity. Both reconfig() and reconfigure() are implemented via
protected methods in ZooKeeper.java
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Randgalt/zookeeper ZOOKEEPER-2642
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/122.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #122
----
commit 3611d18eb73bac5760293730087d2b0c3241b2bc
Author: randgalt <[email protected]>
Date: 2016-12-10T19:33:58Z
Resurrect the reconfig() methods that were in ZooKeeper.java. While 3.5.x
is an alpha there are clients in production that are relying
on the current specification. The reconfig() methods are marked deprecated
to inform that they will be removed later. The "new" methods
in the new class ZooKeeperAdmin were renamed reconfigure() to avoid getting
the deprecation annotation inherited and to provide clarity.
Both reconfig() and reconfigure() are implemented via protected methods in
ZooKeeper.java
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
