[
https://issues.apache.org/jira/browse/ACCUMULO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856996#comment-13856996
]
Mike Drob commented on ACCUMULO-2076:
-------------------------------------
[~kturner] - The {{ZooKeeperInstance(Configuration)}} constructor is still too
much work, I think. The user still has to feed an instance name/id into the
connection. I'm looking for an entry point where the user is willing to assume
that there is a single Accumulo installation and s/he just wants to use that
one. Or if there are multiple, then once of them is located in a more
'conventional' location and takes precedence. Advanced users should absolutely
be able to specify that they want instance X, but that's just not something
that's ever come up for me.
I think Josh is heading down the right path that we need an
{{accumulo-client.xml}} in addition to {{accumulo-site.xml}} but that's a
larger change than I think I want to introduce in a point release.
> 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)
