[ 
https://issues.apache.org/jira/browse/ACCUMULO-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877163#comment-13877163
 ] 

Josh Elser commented on ACCUMULO-2100:
--------------------------------------

Nice -- makes sense. We've had some other discussions about how MAC should 
evolve. Instead of extending the minicluster itself, might it make more sense 
to add something new to the MiniAccumuloConfig?

The changes you have might be a simple workaround for the short-term, but it 
would definitely be good to weigh in on the bigger picture for 
MiniAccumuloCluster (notably, starting a temporary instance, starting a temp 
instance from a real instance, and other things).

> instamo-archetype could use a little clean up
> ---------------------------------------------
>
>                 Key: ACCUMULO-2100
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2100
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: instamo-archetype
>            Reporter: Michael Wall
>            Assignee: Josh Elser
>            Priority: Minor
>
> Some of the things I noticed
> - mvn test fails, because it took longer than 30 secs to startup the MAC on 
> my linux box.
> - README needs to be updated, usage is incorrect
> - pom.xml doesn't hook exec:exec into any lifecycle so you have to call mvn 
> compile exec:exec -Pwhatever
> - Could abstract out a MiniAccumuloClusterWrapper to handle the temp 
> directory clean up and make the usage across the ShellExample, 
> MapReduceExample and ExampleAccumuloUnitTest consistent.  Would also make it 
> easier to implement ACCUMULO-2097 and ACCUMULO-2098
> BTW, I am running this against the origin/1.5 branch, targeting an archetype 
> that is compatible with Accumulo 1.5.0
> Patch coming for review



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to