You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2016/12/07 11:23:58 UTC

[jira] [Created] (ZOOKEEPER-2642) ZOOKEEPER-2014 breaks existing clients for little benefit

Jordan Zimmerman created ZOOKEEPER-2642:
-------------------------------------------

             Summary: ZOOKEEPER-2014 breaks existing clients for little benefit
                 Key: ZOOKEEPER-2642
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2642
             Project: ZooKeeper
          Issue Type: Bug
          Components: c client, java client
    Affects Versions: 3.5.2
            Reporter: Jordan Zimmerman


ZOOKEEPER-2014 moved the reconfig() methods into a new class, ZooKeeperAdmin. It appears this was done to document that these are methods have access restrictions. However, this change breaks Apache Curator (and possibly other clients). Curator APIs will have to be changed and/or special methods need to be added. A breaking change of this kind should only be done when the benefit is overwhelming. In this case, the same information can be conveyed with documentation and possibly a deprecation notice.

Revert the creation of the ZooKeeperAdmin class and move the reconfig() methods back to the ZooKeeper class with additional documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)