accumulo-notifications mailing list archives

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

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

Eric Newton commented on ACCUMULO-878:
--------------------------------------

It is faster, and it works for in-memory unit tests, even for those poor souls who develop
on Windows (eew).  I know that it is used extensively for testing complicated iterator stacks.
Perhaps Josh and/or Bill would like to chime in.
                
> 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