+1 (non-binding) Christopher's comment on -878 [1] echoes my thinking. For me, "mock" means "unit tests", and I'd rather use a mock framework (Easymock, Mockito, whatever) than a running cluster (however lightweight) in unit tests.
[1]: https://issues.apache.org/jira/browse/ACCUMULO-878?focusedCommentId=13504949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13504949 On Thu, Nov 14, 2013 at 3:41 PM, Keith Turner <ke...@deenlo.com> wrote: > Should we deprecate mock accumulo for 1.6.0? This was considered [1] for > 1.5.0. I started thinking about this because I never added conditional > writer to mock. > > [1] : https://issues.apache.org/jira/browse/ACCUMULO-878 > -- | - - - | Bill Havanki | Solutions Architect, Cloudera Government Solutions | - - -
