accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2076) Make it easier to connect to acccumulo
Date Tue, 24 Dec 2013 00:07:51 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856035#comment-13856035
] 

Mike Drob commented on ACCUMULO-2076:
-------------------------------------

Can clients and servers use a different set of zoo keepers? I imagine that those have to be
the same between both, right? So what is the distinction between {{accumulo-site.xml}} and
a client config at that point?

> 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)

Mime
View raw message