accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-14) Transition from full Accumulo mocking
Date Tue, 27 Nov 2012 21:18:58 GMT


Josh Elser commented on ACCUMULO-14:

I wanted to leave some notes about what I'd like to see from MiniAccumuloCluster (perhaps
this is a separate discussion..). I will admit that I haven't dug through the source code

A short wishlist of things I'd like to see from MiniAccumuloCluster (or some mocking framework
which uses it):

* Smoke-test framework for iterators (API to run an iterator over data asserting the same
results while varying things like server-side memory buffer, multiple tservers, adding/removing
split points, etc)
* The ability to run multiple tservers in memory on a single host
* Table configurations and tablet hosting/migration/etc works when having multiple tservers

It would be cool to even make some sort of Maven plugin/archetype that one could include in
their own Maven project to do "more realistic" testing against Accumulo instead of necessarily
depending on a test module in Accumulo? Just a thought, I'm not sure of the best way to bundle

> 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