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
I am fine with this. Any hive committers who wants to volunteer to be
a hcat shepherd is welcome.

On 12/14/12 7:01 AM, "Travis Crawford" <[EMAIL PROTECTED]> wrote:

>Thanks for reviving this thread. Reviewing the comments everyone seems
>to agree HCatalog makes sense as a Hive subproject. I think that's
>great news for the Hadoop community.
>
>The discussion seems to have turned to one of committer permissions. I
>agree with the Hive folks sentiment that its something that must be
>earned. That said, I've found it challenging at times getting patches
>into Hive that would help earn taking on a hive committer
>responsibility.
>
>Proposal: if a couple hive committers can volunteer to be hcat
>shepherds, we can work with the shepherds when making hive changes in
>a timely manor. Conversely, we can help shepherd any hive committers
>who are interested in working more with hcat. There are certainly
>benefits to cross-committership, and this approach could help each
>other build a history of meaningful contributions and earn the
>privilege & responsibility of being committers.
>
>Thoughts?
>
>--travis
>
>
>
>On Thu, Dec 13, 2012 at 11:59 AM, Edward Capriolo <[EMAIL PROTECTED]>
>wrote:
>> I initially was a hesitant of hcatalog mostly because I imagined we
>>would
>> end up in a spot very similar to this.
>>
>> Namely the hcatlog folks are interested in making a metastore to support
>> pig, hive, and map reduce. However I get the impression that many in
>>hive
>> do not care much to have a metastore that caters to everyone. Their
>>needs
>> are only based on what hive needs. Which I believe is the wrong way to
>>look
>> at this situation.
>>
>> I though to reply to this thread because I have been following this
>>Jira:
>> https://issues.apache.org/jira/browse/HIVE-3752
>>
>> On a high level I do not like this duplication of effort and code. If
>>hive
>> is compatible with hcatalog I do not see why we put off merging the two
>>at
>> all. Hive users would get an immediate benefit if Hive used hcatalog
>>with
>> no apparent downside. Meanwhile we are putting this off and staying in
>>this
>> awkward transition phase.
>>
>> Personally, I do not have a problem being a hive committer and not
>>having
>> hcatalog commit. None of the hive work I have done has ever touched the
>> metastore. Also of the thousands of jiras and features we have added
>>only a
>> small portion require metastore changes.
>>
>> As long as a couple active users have commit on hive and the suggested
>> hcatalog subproject I do not think not having commit will be a
>>roadblock in
>> moving hive forward.
>>
>>
>> On Mon, Dec 3, 2012 at 6:22 PM, Alan Gates <[EMAIL PROTECTED]>
>>wrote:
>>
>>> I am not sure where we are on this discussion.  So far those who have
>>> chimed in seemed generally positive (Namit, Edward, Clark, Alexander).
>>>  Namit and I have different visions for what the committership might
>>>look
>>> like, so I'd like to hear from other Hive PMC members what their view
>>>is on
>>> this.  I have to say from an HCatalog perspective the proposition is
>>>much
>>> less attractive without some commit rights.
>>>
>>> On a related note, people should be aware of these threads in the
>>> Incubator list:
>>>
>>>
>>>http://mail-archives.apache.org/mod_mbox/incubator-general/201211.mbox/%
>>>3CCAGU5spdWHNtJxgQ8f%3DnPEXx9xNLjyjOYaFfnSw4EyAjgm1c46w%40mail.gmail.com
>>>%3E
>>>
>>>
>>>
>>>http://mail-archives.apache.org/mod_mbox/incubator-general/201211.mbox/%
>>>3CCAKQbXgDZj_zMj4qSodXjMHV7xQZxpcY1-35cvq959YKLNd6tJQ%40mail.gmail.com%3
>>>E
>>>
>>> For those not inclined to read all the mails in the threads I will
>>> summarize (though I urge all PMC members of Hive and PPMC members of
>>>HCat
>>> to read both mail threads because this is highly relevant to what we
>>>are
>>> discussing).  There are two salient points in these threads:
>>>
>>> 1) It is not wise to build a subproject that is distinct from the main
>>> project in the sense that it has separate community members interested
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