Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # general >> [DISCUSS] Spin out MR, HDFS and YARN as their own TLPs and disband Hadoop umbrella project


Copy link to this message
-
Re: [DISCUSS] Spin out MR, HDFS and YARN as their own TLPs and disband Hadoop umbrella project
Another way around is to produce more than one common's artifacts that
will provide some logic split for the downstream projects like MR, and so on.

Cos

On Wed, Aug 29, 2012 at 10:26AM, Suresh Srinivas wrote:
> > > - I agree with Arun that the common can move with HDFS.
> >
> > So, this would mean that a bunch of common functionality needed by
> > other TPLs (YARN, MR, HBASE) which is not required by HDFS will end up
> > in HDFS. I'm not necessary against that but it should be well
> > understood/expected/accepted by HDFS TPL, right?
> >
>
> RPC is the main common functionality (not used by HBase). Others are some
> utilities related to native i/o, Configuration and other helper utils.
> Other than RPC projects we can move utils specific to a project into that
> project. In some cases if there is code duplication, that is fine. We can
> make a call on those on case by case basis.
>
> --
> http://hortonworks.com/download/
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB