[
https://issues.apache.org/jira/browse/ACCUMULO-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651058#comment-13651058
]
Corey J. Nolet commented on ACCUMULO-1378:
------------------------------------------
bq. are you proposing reorganizing the implementation of MAC or API changes?
I'm referring to reorg of implementations for better code reuse- not API
changes. You had me thinking about having a SingleNodeAccumulo that was
different from the MiniAccumuloCluster. If we did that, many things would
remain the same in both- processes get spun up, ports get configured, LogWriter
gets created, shutdown hooks get registered, and vmargs optionally get attached
to the processes for remote debugging. I've been teetering back and forth about
this. On one hand, if the only difference between the two are the ability to
re-use a directory/configuration, that doesn't seem to me like enough of a
difference to separate them. On the other hand, if we want to treat one as a
quick integration test environment and the other as a full development
environment then we can define a broader set of features that differentiate the
two. The latter seems like grounds for separation.
> Allow MiniAccumulo cluster configured directory to be used across different
> runs
> --------------------------------------------------------------------------------
>
> Key: ACCUMULO-1378
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1378
> Project: Accumulo
> Issue Type: Sub-task
> Reporter: Corey J. Nolet
> Assignee: Corey J. Nolet
> Priority: Minor
>
> Currently, the MiniAccumuloCluster assumes it should always create the
> directory structure and throws an exception if the passed in directory has
> anything in it.
--
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: http://www.atlassian.com/software/jira
