accumulo-notifications mailing list archives

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

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

William Slacum commented on ACCUMULO-878:
-----------------------------------------

I'm leaning towards keeping it. There have been several behavioral differences between MockAccumulo
and a real instance that can go undetected (and possibly remain undocumented), but I prefer
to have some framework that is completely in memory and doesn't dirty the user's file system.
                
> 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