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 2013/01/11 22:16:12 UTC

[jira] [Commented] (ACCUMULO-878) Decide fate of Mock Accumulo

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

Keith Turner commented on ACCUMULO-878:
---------------------------------------

There does not seem to be a consensus for deprecating mock for 1.5.  Could possibly reconsider at 1.6.   Looking at the comments 2 were for deprecating 3 for not deprecating.  I will add some javadocs to MocKInstance.
                
> 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