You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2014/01/13 20:47:53 UTC

[jira] [Resolved] (ACCUMULO-2151) Separate API from implementation of mini accumulo

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

Keith Turner resolved ACCUMULO-2151.
------------------------------------

    Resolution: Fixed

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