Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper, mail # dev - Re: [PROPOSAL] Accumulo for the Apache Incubator


Copy link to this message
-
Re: [PROPOSAL] Accumulo for the Apache Incubator
Mahadev Konar 2011-09-02, 16:45
Nice!
Is this related to HBase? Or similar to it?

mahadev

On Fri, Sep 2, 2011 at 9:27 AM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
> FYI, another project using ZK -- woot!!! (note that they have their
> own WAL - perhaps a good application for BookKeeper?)
>
> ---------- Forwarded message ----------
> From: Billie J Rinaldi <[EMAIL PROTECTED]>
> Date: Fri, Sep 2, 2011 at 8:45 AM
> Subject: [PROPOSAL] Accumulo for the Apache Incubator
> To: [EMAIL PROTECTED]
>
>
> Greetings,
>
> I would like to propose Accumulo to be an Apache Incubator project.
> Accumulo is a distributed key/value store that provides expressive
> cell-level access labels and a server-side programming mechanism that
> can modify key/value pairs at various points in the data management
> process.  It is based on Google's BigTable design and runs over Apache
> Hadoop and Zookeeper.
>
> Here is a link to the proposal in the Incubator wiki:
> http://wiki.apache.org/incubator/AccumuloProposal
>
> I've also pasted the initial contents below.
>
> Thanks,
> Billie Rinaldi
>
>
> = Accumulo Proposal >
> == Abstract => Accumulo is a distributed key/value store that provides expressive,
> cell-level access labels.
>
> == Proposal => Accumulo is a sorted, distributed key/value store based on Google's
> BigTable design.  It is built on top of Apache Hadoop, Zookeeper, and
> Thrift.  It features a few novel improvements on the BigTable design
> in the form of cell-level access labels and a server-side programming
> mechanism that can modify key/value pairs at various points in the
> data management process.
>
> == Background => Google published the design of BigTable in 2006.  Several other open
> source projects have implemented aspects of this design including
> HBase, CloudStore, and Cassandra.  Accumulo began its development in
> 2008.
>
> == Rationale => There is a need for a flexible, high performance distributed key/value
> store that provides expressive, fine-grained access labels.  The
> communities we expect to be most interested in such a project are
> government, health care, and other industries where privacy is a
> concern.  We have made much progress in developing this project over
> the past 3 years and believe both the project and the interested
> communities would benefit from this work being openly available and
> having open development.
>
> == Current Status =>
> === Meritocracy ==> We intend to strongly encourage the community to help with and
> contribute to the code.  We will actively seek potential committers
> and help them become familiar with the codebase.
>
> === Community ==> A strong government community has developed around Accumulo and
> training classes have been ongoing for about a year.  Hundreds of
> developers use Accumulo.
>
> === Core Developers ==> The developers are mainly employed by the National Security Agency,
> but we anticipate interest developing among other companies.
>
> === Alignment ==> Accumulo is built on top of Hadoop, Zookeeper, and Thrift.  It builds
> with Maven.  Due to the strong relationship with these Apache
> projects, the incubator is a good match for Accumulo.
>
> == Known Risks => === Orphaned Products ==> There is only a small risk of being orphaned.  The community is
> committed to improving the codebase of the project due to its
> fulfilling needs not addressed by any other software.
>
> === Inexperience with Open Source ==> The codebase has been treated internally as an open source project
> since its beginning, and the initial Apache committers have been
> involved with the code for multiple years.  While our experience with
> public open source is limited, we do not anticipate difficulty in
> operating under Apache's development process.
>
> === Homogeneous Developers ==> The committers have multiple employers and it is expected that
> committers from different companies will be recruited.
>
> === Reliance on Salaried Developers ==> The initial committers are all paid by their employers to work on