accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2151) Separate API from implementation of mini accumulo
Date Mon, 13 Jan 2014 18:52:52 GMT

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

ASF subversion and git services commented on ACCUMULO-2151:
-----------------------------------------------------------

Commit 9d1e171e248a0809c5b2551b87c81d657378822c in branch refs/heads/1.6.0-SNAPSHOT from [~keith_turner]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=9d1e171 ]

ACCUMULO-2151 separated MAC API from implementation


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

Mime
View raw message