[
https://issues.apache.org/jira/browse/ACCUMULO-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997111#comment-13997111
]
Josh Elser commented on ACCUMULO-1612:
--------------------------------------
[~ryanleary], while MockAccumulo is a nice, quick way a "mostly correct"
environment to do some basic testing against Accumulo, it's a large burden both
to maintain and implement. Any feature that is created, now also has to be
implemented to work with MockAccumulo. As such, we've had a fair share of bugs
purely inside of MockAccumulo where the Mock implementation was either buggy or
did not provide an accurate test environment.
As such, we've been making more efforts behind MiniAccumuloCluster to address
its deficiencies (slower start time and requiring more resources being the
biggest two offenders) as it provides a (near) 100% accurate testing harness
that you can use with great certainty to test out some code before putting it
on a real Accumulo instance. That's my assumption as to why this is a won't
fix. I would not expect a contribution to be turned away that implements
ConditionalMutations in MockAccumulo; it is just not planned to be implemented.
> Add conditional writer to mock accumulo
> ---------------------------------------
>
> Key: ACCUMULO-1612
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1612
> Project: Accumulo
> Issue Type: Sub-task
> Components: client, tserver
> Reporter: Keith Turner
>
> Could adapt the conditional writer prototype[1] as the mock implementation.
> [1]: https://github.com/keith-turner/ACCUMULO-1000
--
This message was sent by Atlassian JIRA
(v6.2#6252)
