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
I am +1 for splitting up the projects. This is the step in the right
direction. There will be challenges along the way. I am confident we can
solve them.

Robert and Alejandro have brought up good questions. Here are my thoughts:
- For first one or two releases all the projects can coordinate and do the
releases together. This should help simplify the immediate work needed.
This should also help in us meeting the release timelines that we are
working towards. As the split makes progress, this cross project
coordination will no longer be necessary. I volunteer to RM these releases
and do the needed co-ordination from HDFS.
- As regards to APIs, currently we have LimitedPrivate APIs for related
projects. This has been used by HBase as well. We need to think about a
timeline by when we can mark these APIs stable. They should remain
LimitedPrivate. Any rare changes to APIs requires only co-ordination among
the projects and no user applications (which we have not control over) is
affected.
- I agree with Arun that the common can move with HDFS.

Regards,
Suresh

On Wed, Aug 29, 2012 at 9:31 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:

>
> On Aug 28, 2012, at 8:50 PM, Alejandro Abdelnur wrote:
>
> > Chris, thanks for initiating the discussion.
>
> Likewise, thanks Chris!
>
> >
> > IMO a pre-requisite to this is to figure out how we'll handle the
> following:
> >
>
>
> Good points - I'd recommend we keep Common and HDFS in the same project.
> Yes, MR/YARN will need some changes in Common occasionally, but core pieces
> like RPC have been maintained by HDFS folks over time anyway e.g. move to
> ProtoBufs were led by Sanjay, Suresh, Todd, Jitendra et al.
>
> We can move SequenceFile into MR if necessary and keep same package names
> for compatibility.
>
> We should, of course, stop tweaking things in different projects in the
> same jira - we've been reasonably good at not doing that.
>
> Thoughts?
>
> Arun
>
> > * Where does common stuff lives?
> > * What are the public interfaces of each project (towards the other
> projects)?
> > * How do we do development/releases? In tandem? Separate? How this
> > will work in practice, currently we are constantly tweaking things
> > inter-projects, sometimes in the same JIRAs, sometimes in follow up
> > JIRAs.
> >
> > Thoughts?
> >
> > Thxs.
> >
> > On Tue, Aug 28, 2012 at 7:33 PM, Mattmann, Chris A (388J)
> > <[EMAIL PROTECTED]> wrote:
> >> [decided to minimize traffic and to simply put this in one thread]
> >>
> >> Hi Guys,
> >>
> >> See the recent discussion on these threads:
> >>
> >> YARN as its own Hadoop "sub project": http://s.apache.org/WW1
> >> Maintain a single committer list for the Hadoop project:
> http://s.apache.org/Owx
> >>
> >> ...and just pay attention to the Hadoop project over the last 3-4
> years. It's operating
> >> as a single project, that's masking separate communities that
> themselves are really
> >> separate ASF projects.
> >>
> >> At the ASF, this has been a problem area called "umbrella" projects and
> over the years,
> >> all I've seen from them is wasted bandwidth, artificial barriers and
> the inventions of
> >> new ways to perform process mongering and to reduce the fun in
> developing software
> >> at this fantastic foundation.
> >>
> >> I've talked about umbrella projects enough. We've diverted conversation
> enough.
> >> Enough people have tried to act like there is some technical mumbo
> jumbo that is
> >> preventing the eventual act of higher power that I myself hope comes
> should these
> >> discussions prove unfruitful through normal means.
> >>
> >> *these. are. separate. projects.*
> >>
> *there.are.not.blocker.issues.from.spinning.out.these.projects.as.their.own.communities*
> >>
> >> In this email: http://s.apache.org/rSm
> >>
> >> And in the 2 subsequent follow ons in that thread, I've outlined a
> process that I'll copy
> >> through below for splitting these projects into their own TLPs:
> >>
> >> -----snip
> >> Process:
> >>
> >> 0. [DISCUSS] thread for <TLP name> in which you talk about #1 and #2
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