You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2014/01/10 00:53:50 UTC
[jira] [Created] (ACCUMULO-2167) remove deprecation from
ZooKeeperInstance(String, String) constructor
Keith Turner created ACCUMULO-2167:
--------------------------------------
Summary: remove deprecation from ZooKeeperInstance(String, String) constructor
Key: ACCUMULO-2167
URL: https://issues.apache.org/jira/browse/ACCUMULO-2167
Project: Accumulo
Issue Type: Bug
Reporter: Keith Turner
Assignee: Keith Turner
Fix For: 1.6.0
In 1.6.0-SNAPSHOT the ZooKeeperInstance(String, String) constructor was deprecated. It does not seem there is a compelling reason to do this. Below are some reasons I can think of not to do it.
* In 1.6.0 you still need to know an instance name and zookeepers to create a ZookeeperInstance programmatically. So its not like its reason for being is no longer valid.
* Its a nice conveince method for new code written against accumulo (its shorter than {{new ClientConfiguration()..withInstance(instanceName).withZkHosts(zooKeepers)}}
* Most existing code using the API probably uses it. Why annoy users unnecessarily?
* There is no maintenance burden for keeping the method
I think all of the other constructors that were deprecated should stay deprecated. Its likely those constructors are not used, and if their functionality is needed then ClientConfiguration can be used.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)