You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by fpj <gi...@git.apache.org> on 2017/01/11 14:50:14 UTC

[GitHub] zookeeper pull request #122: [ZOOKEEPER-2642] Resurrect the reconfig() metho...

Github user fpj commented on a diff in the pull request:

    https://github.com/apache/zookeeper/pull/122#discussion_r95591971
  
    --- Diff: src/docs/src/documentation/content/xdocs/zookeeperReconfig.xml ---
    @@ -300,6 +300,11 @@ server.3=125.23.63.25:2782:2785:participant</programlisting>
                   from ZooKeeper class, and use of this API requires ACL setup and user
                   authentication (see <xref linkend="sc_reconfig_access_control"/> for more information.).
                 </para>
    +
    +            <para>Note: for temporary backward compatibility, the reconfig() APIs will remain in ZooKeeper.java
    +              where they were for a few alpha versions of 3.5.x. However, these APIs are deprecated and users
    +              should move to the reconfig() APIs in ZooKeeperAdmin.java.
    --- End diff --
    
    Small typo: `reconfig()` should be `reconfigure()`.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---