accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (Updated) (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-14) Transition from fulll Accumulo mocking
Date Mon, 28 Nov 2011 22:47:41 GMT


Jesse Yates updated ACCUMULO-14:

    Attachment: java_ACCUMULO-14-start.patch

Initial work for getting a more 'real' mockAccumulo.

Essentially, it uses a local ZK cluster and the local file system to run accumulo, using all
the 'real' classes.

This biggest slowdown is in waiting for the tabletserver to come online. However, it is actually
pretty snappy to startup.

Adding this patch to get review of the overall design. Its it NOT a final version, or even
really that all that close. I just want to make sure I'm not wasting too much time.

So far, had to do a little work making sure the TS and Master could be started and also did
an in-memory version of the Initialize class (more copy and paste, as I was just trying to
get something up). However, everything runs in the same JVM in different threads.

Also, I'm looking for suggestions on the best way to shutdown the cluster, rather than just
killing the threads.

> Transition from fulll Accumulo mocking
> --------------------------------------
>                 Key: ACCUMULO-14
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: Jesse Yates
>             Fix For: 1.5.0
>         Attachments: 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:!default.jspa
For more information on JIRA, see:


View raw message