Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 7 Jan 2014 17:33:53 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12687696.1389115990859.55714.1389116033055@arcas>
In-Reply-To: <JIRA.12687696.1389115990859@arcas>
References: <JIRA.12687696.1389115990859@arcas>
Subject: [jira] [Created] (ACCUMULO-2151) Separate API from implementation
 of mini accumulo
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Keith Turner created ACCUMULO-2151:
--------------------------------------

             Summary: Separate API from implementation of mini accumulo
                 Key: ACCUMULO-2151
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2151
             Project: Accumulo
          Issue Type: Improvement
            Reporter: Keith Turner
            Assignee: Keith Turner
             Fix For: 1.6.0


Mini Accumulo has two primary purposes :

 # Allows users to easily test their code against a real Accumulo instance
 # Allows Accumulo to test itself

The second use case requires APIs not needed by the first uses case.  Currently the mini accumulo API and implementation are in the same class. Separating these into two classes would make it easier to support the second use case w/o cluttering the user API.   Also its nice to be able to change the APIs needed for the second use case on a whim, if these APIs are mixed in with the user API then this flexibility it lost.   


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)