accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-878) Decide fate of Mock Accumulo
Date Tue, 27 Nov 2012 21:12:57 GMT

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

Josh Elser commented on ACCUMULO-878:
-------------------------------------

There were some issues previously inside of MockAccumulo that caused things to not run in
mock but run correctly on a real instance. Until we have something that can provide an equivalent
in-memory instance that can be used for testing, I'm hesitant to mark MockAccumulo as deprecated.
Figuring out the actual scope/functionality of MiniAccumuloCluster is dependent on this, I
believe.
                
> Decide fate of Mock Accumulo
> ----------------------------
>
>                 Key: ACCUMULO-878
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-878
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Keith Turner
>             Fix For: 1.5.0
>
>
> Now that we have MiniAccumuloCluster, we need to decide what we want to do with Mock
Accumulo.  Seems like there are two options for 1.5, either deperecate it or continue to maintain
it.  The main advantage of keeping it around is that its fast, however its behavior is not
always correct (ACCUMULO-664, ACCUMULO-843, ACCUMULO-877).  If we choose to deperecate it,
we could probably close out the tickets against mock for 1.5.
> What are peoples thoughts?  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message