[ https://issues.apache.org/jira/browse/ZOOKEEPER-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751303#comment-15751303 ]
Jordan Zimmerman commented on ZOOKEEPER-2642: --------------------------------------------- The test failures seem to be a chronic issue in ZK in general and not related to this PR: https://issues.apache.org/jira/browse/ZOOKEEPER-2080?jql=project%20%3D%20ZOOKEEPER%20AND%20text%20~%20%22AssertionFailedError%3A%20waiting%20for%20server%22 > 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 > Assignee: Jordan Zimmerman > Priority: Blocker > Attachments: ZOOKEEPER-2642.patch, ZOOKEEPER-2642.patch, > ZOOKEEPER-2642.patch, ZOOKEEPER-2642.patch > > > 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)