accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-14) Transition from full Accumulo mocking
Date Thu, 22 Nov 2012 00:18:58 GMT


Keith Turner commented on ACCUMULO-14:

bq. Maybe this should stay as a separate project? I say that so that an Accumulo release would
not be delayed by needing to keep instamo in sync. It might even be great to have instamo
able to work with multiple accumulo releases at once

I just checked in something to examples/instamo.  It should not hold up a release in anyway.
The Accumulo web page can be updated to point to this example anytime after 1.5.0 is released.
 The instamo github project contained three major components a pom, example code, and MiniAccumuloCluster.
  Now that MiniAccumuloCluster is part of Accumulo  it will work with any version of Accumulo
from 1.5.0 forward as long as versions match.  For example you will need to use accumulo-test-1.5.0
with accumulo-core-1.5.0.   I think creating a version of MiniAccumuloCluster that works with
any version of Accumulo would result in a very convoluted piece of code over time.  I think
having a version of MiniAccumuloCluster that only works with one version of Accumulo is much
easier to maintain.  The pom and example code in the instamo git hub project just become examples
for in Accumulo source.
> Transition from full Accumulo mocking
> -------------------------------------
>                 Key: ACCUMULO-14
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: Jesse Yates
>            Assignee: Eric Newton
>             Fix For: 1.5.0
>         Attachments: java_ACCUMULO-14-start-formatted.patch, java_ACCUMULO-14-start.patch
> Original discussion present here:
> Jesse Yates: "Maintaining a real instance and a mock instance ends up creating a lot
of extra work for dev's by ensuring that there impls are kept synchronized....[using a real]
instance of Accumulo running on the local file system. This would mean less work in the long
run to maintain a separate instance and better testing for users and new features."
> Keith Turner: "its very fast to create a mock instance which means that unit test run
very quickly...[and] its all in process which is useful for debugging...making mock leverage
more of the actual accumulo code, but possibly keep it in process for speed and debugging."
> This ticket is to track the discussion and development of a less mocked test instance
of accumulo, that relies more heavily on the actual implementation, rather than parallel mocking

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:

View raw message