accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1405) Package MiniAccumuloCluster so that a user can interact without Hadoop/ZooKeeper installed
Date Wed, 15 May 2013 03:35:15 GMT


Keith Turner commented on ACCUMULO-1405:

bq. There's a lot of blocks already in place with the Instamo stuff.

I would not say the blocks are in place at this point in time.  Maybe after ACCUMULO-1378
is complete, instamo could leverage that work.  When a lot of the tickets under ACCUMULO-1386
are complete and its easy to run a single node accumulo, how do we package that and make it
available to users?  Keep in mind that users will want to stop and start this instance, its
not transient.  Users will also want to configure it.   Maybe maven is a way to do this, I
am not really sure at this point.   Seems like it would be something different than instamo,
maybe a maven plugin for managing a single node accumulo instance.  Will this work w/ native
maps? Another option is creating a tarball, rpm, and deb.  I think it would be useful to develop
a list of the pros and cons of each approach.  I agree w/ [~medined] we do want to be cognizant
of the maintenance tail of whatever we create.  We will have to continue to support in 1.7,
> Package MiniAccumuloCluster so that a user can interact without Hadoop/ZooKeeper installed
> ------------------------------------------------------------------------------------------
>                 Key: ACCUMULO-1405
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Corey J. Nolet
>            Assignee: Corey J. Nolet
>             Fix For: 1.6.0
> Accumulo's packaging is currently very lightweight because many libraries, like Apache
Commons, are being pulled from Hadoop & ZooKeeper's classpaths. It will not allow the
MAC to be run from accumulo-start, however, without Hadoop and ZooKeeper installed.

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