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
Hive >> mail # dev >> [DISCUSS] HCatalog becoming a subproject of Hive


Copy link to this message
-
Re: [DISCUSS] HCatalog becoming a subproject of Hive
Alan's proposal sounds like a good idea to me.

+1

On Dec 18, 2012 5:36 PM, "Travis Crawford" <[EMAIL PROTECTED]> wrote:

> Alan, I think your proposal sounds great.
>
> --travis
>
> On Tue, Dec 18, 2012 at 1:13 PM, Alan Gates <[EMAIL PROTECTED]> wrote:
> > Carl, speaking just for myself and not as a representative of the HCat
> PPMC at this point, I am coming to agree with you that HCat integrating
> with Hive fully makes more sense.
> >
> > However, this makes the committer question even thornier.  Travis and
> Namit, I think the shepherd proposal needs to lay out a clear and time
> bounded path to committership for HCat committers.  Having HCat committers
> as second class Hive citizens for the long run will not be healthy.  I
> propose the following as a starting point for discussion:
> >
> > All active HCat committers (those who have contributed or committed a
> patch in the last 6 months) will be made committers in the HCat portion
> only of Hive.  In addition those committers will be assigned a particular
> shepherd who is a current Hive committer and who will be responsible for
> mentoring them towards full Hive committership.  As a part of this
> mentorship the HCat committer will review patches of other contributors,
> contribute patches to Hive (both inside and outside of HCatalog), respond
> to user issues on the mailing lists, etc.  It is intended that as a result
> of this mentorship program HCat committers can become full Hive committers
> in 6-9 months.  No new HCat only committers will be elected in Hive after
> this.  All Hive committers will automatically also have commit rights on
> HCatalog.
> >
> > Alan.
> >
> > On Dec 14, 2012, at 10:05 AM, Carl Steinbach wrote:
> >
> >> On a functional level I don't think there is going to be much of a
> >> difference between the subproject option proposed by Travis and the
> other
> >> option where HCatalog becomes a TLP. In both cases HCatalog and Hive
> will
> >> have separate committers, separate code repositories, separate release
> >> cycles, and separate project roadmaps. Aside from ASF bureaucracy, I
> think
> >> the only major difference between the two options is that the subproject
> >> route will give the rest of the community the false impression that the
> two
> >> projects have coordinated roadmaps and a process to prevent overlapping
> >> functionality from appearing in both projects. Consequently, If these
> are
> >> the only two options then I would prefer that HCatalog become a TLP.
> >>
> >> On the other hand, I also agree with many of the sentiments that have
> >> already been expressed in this thread, namely that the two projects are
> >> closely related and that it would benefit the community at large if the
> two
> >> projects could be brought closer together. Up to this point the major
> >> source of pain for the HCatalog team has been the frequent necessity of
> >> making changes on both the Hive and HCatalog sides when implementing new
> >> features in HCatalog. This situation is compounded by the ASF
> requirement
> >> that release artifacts may not depend on snapshot artifacts from other
> ASF
> >> projects. Furthermore, if Hive adds a dependency on HCatalog then it
> will
> >> be subject to these same problems (in addition to the gross circular
> >> dependency!).
> >>
> >> I think the best way to avoid these problems is for HCatalog to become a
> >> Hive submodule. In this scenario HCatalog would exist as a subdirectory
> in
> >> the Hive repository and would be distributed as a Hive artifact in
> future
> >> Hive releases. In addition to solving the problems I mentioned earlier,
> I
> >> think this would also help to assuage the concerns of many Hive
> committers
> >> who don't want to see the MetaStore split out into a separate project.
> >>
> >> Thanks.
> >>
> >> Carl
> >>
> >> On Thu, Dec 13, 2012 at 7:59 PM, Namit Jain <[EMAIL PROTECTED]> wrote:
> >>
> >>> I am fine with this. Any hive committers who wants to volunteer to be
> >
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