Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 14 May 2014 18:57:15 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12685871.1387566203253.347667.1400093835572@arcas>
In-Reply-To: <JIRA.12685871.1387566203253@arcas>
References: <JIRA.12685871.1387566203253@arcas>
Subject: [jira] [Updated] (ACCUMULO-2076) Make it easier to connect to
 acccumulo
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated ACCUMULO-2076:
---------------------------------

    Priority: Blocker  (was: Minor)

> Make it easier to connect to acccumulo
> --------------------------------------
>
>                 Key: ACCUMULO-2076
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2076
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Mike Drob
>            Priority: Blocker
>             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.2#6252)