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 Fri, 16 Nov 2012 02:03:12 GMT


Keith Turner commented on ACCUMULO-14:

Just checked in MiniAccumuloCluster r1410144

I am trying to decide where the best place to put something like instamo in svn.  A simple
self contained maven project that uses the 1.5 MiniAccumuloCluster.   Once 1.5 is released
I want to put simple straight forward instructions on how to download and run it on the Accumulo
web page.   Currently thinking of creating a contrib/instamo or trunk/examples/instamo.  
Could have something like the following on the Accumulo web page showing how to get up and
running against Accumulo in minutes.

  svn export
  cd instamo
  vim src/main/java/instamo/
  mvn package
  mvn exec:exec
> 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