[
https://issues.apache.org/jira/browse/ACCUMULO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860242#comment-13860242
]
Keith Turner commented on ACCUMULO-2076:
----------------------------------------
bq. the first thing I thought about was the potential confusion over adding
something like this to the 5th bugfix release to a version of Accumulo that's
already about a year old (1.4.5).
Another comment I have made before about adding APIs to older release is that
you may become prematurely committed to it (i.e. a critical bug in 1.4.4 could
necessitate the quick release of 1.4.5 w/ whatever is currently in the branch).
Making API changes in point release allows consideration of a batch of API
changes together rather considering them individually. IMO evaluating a batch
of API changes together allows the chance to produce a better API.
> Make it easier to connect to acccumulo
> --------------------------------------
>
> Key: ACCUMULO-2076
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2076
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Reporter: Mike Drob
> Priority: Minor
> Fix For: 1.7.0
>
>
> Given a program that has {{accumulo-site.xml}} on its classpath, we should be
> able to abstract away from the user the steps for connecting to accumulo. I'm
> thinking that we need to expose something like HdfsZooInstance through the
> client API, but not exactly that, since HZI looks like it carries some extra
> functionality.
> # Determine the backing file system
> # Get Instance ID from the FS.
> # Get ZooServers from accumulo-site.xml
> # Get Instance Name from ZK.
> # Create an Instance and hand it to the user.
> If this already exists in master, then maybe we need to do a better job of
> documenting. Or a better job of educating me.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
