Hello Hive community. It is time for HCatalog to graduate from the Apache
Incubator. Given the heavy dependence of HCatalog on Hive the HCatalog
community agreed it made sense to explore graduating from the Incubator to
become a subproject of Hive (see
http://mail-archives.apache.org/mod_mbox
I like the idea of Hcatalog becoming a Hive sub-project. The
enhancements/bugs in the serde/metastore areas can indirectly
benefit the hive community, and it will be easier for the fix to be in one
place. Having said that, I don't see serde/metastore
moving out of hive into a separate component. Th
Like it too.
+1
Thanks,
Alex
On Nov 5, 2012, at 5:35 AM, Namit Jain wrote:
> I like the idea of Hcatalog becoming a Hive sub-project. The
> enhancements/bugs in the serde/metastore areas can indirectly
> benefit the hive community, and it will be easier for the fix to be in one
> place. Havi
+1 for that. I like it.
2012/11/5 Alexander Lorenz :
> Like it too.
> +1
>
> Thanks,
> Alex
>
> On Nov 5, 2012, at 5:35 AM, Namit Jain wrote:
>
>> I like the idea of Hcatalog becoming a Hive sub-project. The
>> enhancements/bugs in the serde/metastore areas can indirectly
>> benefit the hive com
That is a good idea. I would really like to see hcatalog be a sub
project and then have hive use remove it's metastore code in favour of
hcatalog. How should we coordinate this?
Edward
On Mon, Nov 5, 2012 at 6:41 AM, Clark Yang (杨卓荦)
wrote:
> +1 for that. I like it.
>
> 2012/11/5 Alexander Loren
On Nov 4, 2012, at 8:35 PM, Namit Jain wrote:
> I like the idea of Hcatalog becoming a Hive sub-project. The
> enhancements/bugs in the serde/metastore areas can indirectly
> benefit the hive community, and it will be easier for the fix to be in one
> place. Having said that, I don't see serde/me
Alan, that would not be a good idea. Metastore code is part of hive code,
and it
would be safer if only Hive committers had commit access to that.
On 11/6/12 11:25 PM, "Alan Gates" wrote:
>
>On Nov 4, 2012, at 8:35 PM, Namit Jain wrote:
>
>> I like the idea of Hcatalog becoming a Hive sub-proje
I would suggest looking over the patch history of HCat committers. I think
most of them have already contributed a number of patches to the metastore.
All are certainly aware of how to run Hive unit tests and have an understanding
of how Hive works. So I don't think it's fair to say they woul
The same criteria should be applied to all Hive committers. Only a
committer should be able to commit code.
I don¹t think we should bend this rule. Metastore is not a separate
project, but a integral part of hive.
-namit
On 11/12/12 10:32 PM, "Alan Gates" wrote:
>I would suggest looking over t
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 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 t
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 somethi
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" 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 new
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 s
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
Alan, I think your proposal sounds great.
--travis
On Tue, Dec 18, 2012 at 1:13 PM, Alan Gates 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.
>
> Howev
Alan's proposal sounds like a good idea to me.
+1
On Dec 18, 2012 5:36 PM, "Travis Crawford" wrote:
> Alan, I think your proposal sounds great.
>
> --travis
>
> On Tue, Dec 18, 2012 at 1:13 PM, Alan Gates wrote:
> > Carl, speaking just for myself and not as a representative of the HCat
> PPMC
I don’t agree with the proposal. It is impractical to have a Hcat committer
with commit access to Hcat only portions of Hive. We cannot guarantee that
a Hcat
committer will become a Hive committer in 6-9 months, that depends on what
they do
in the next 6-9 months.
The current Hcat committers shoul
Actually I don't understand why getting Hcat folks as committers on Hive is
a problem. Hive itself became a subproject of Hadoop when it started with
all the Hive committers becoming Hadoop committers. And of course everyone
maintained the discipline that they commit in parts of the code that they
I agree with Ashish.
When Hcat becomes a subproject of Hive, all Hcat committers should
immediately become Hive committers.
After all, that worked well for Hadoop, where all Hadoop committers can
commit to all Hadoop code (common/HDFS/MapReduce), but not all do, instead
focusing only on their are
I agree with Namit on this issue. I don't think it's fair to the
existing group of Hive contributors to give preferential
treatment to HCat committers, or to automatically promote them to
full committer status on the Hive project.
On Thu, Dec 20, 2012 at 1:10 PM, Bhandarkar, Milind <
milind.bhanda
> Would the project not benefit in the long run if Hcat is
> brought in and some day becomes the default metastore for Hive.
Folks, can we please try to keep this straight? HCatalog on its own does
not provide any support for metadata. It is a set of wrapper APIs that make
Hive's metastore and se
hmm... why is this considered "preferential treatment"?
All the work for HCat is in the public domain so we can really evaluate
whether they have been following apache practices - the fact that they are
graduating from the incubator would seem to indicate that they have been
doing so. If this code
We are certainly not marketeers and no one as far as I know is teeing up
for such a campaign. The intent here is certainly not to claim how great
HCatalog is or how great Hive is. The intent here is to see what is best
for the project and how great both are together.
Ashish
On Thu, Dec 20, 2012
Namit,
I was not proposing that promotion to full committership would be automatic. I
assume it would still be done via a vote by the PMC. I agree that we cannot
_guarantee_ committership for HCat committers in 6-9 months. But I am trying
to lay out a clear path they can follow. If they don
Carl,
I think Ashish is trying to avoid exactly this issue of any preferential
treatment to Hcat committers *becoming* Hive committers. If Hcatalog as a
subproject of Hive is accepted, both of us are advocating Hcat committers
becoming Hive committers immediately.
If you read Ashish's comment, it
I am really looking forward to the headline that "Hive Metastore now
provides metadata for platforms other than Hive".
I think that would demonstrate the flexibility of Hive metastore to the
world.
Even if some people consider this a purely "marketing message", the
flexibility of the APIs do appe
+1.
Putting my marketing hat on (I don¹t think marketeers is a four-letter
word), touting Hive metastore as a sufficient metadata solution for other
platforms such as MR and Pig, is nothing to be ashamed of.
- Milind
---
Milind Bhandarkar
Chief Scientist,
Machine Learning Platforms,
Greenplum, A
So what is the next step here? As far as I can tell all agree that moving HCat
into Hive is the right thing to do, but there is a fairly polarized division on
how to handle the commit rights. Given that I re-propose my compromise. Like
all good compromises most everyone hates it. But I think
Hi Alan,
I agree that submitting this for a vote is the best option.
> If anyone has additional proposed modifications please make them.
> Otherwise I propose that the Hive PMC vote on this proposal.
>
In order for the Hive PMC to be able to vote on these changes they need to
be expressed in t
If you think that's the best path forward that's fine. I can't call a vote I
don't think, since I'm not part of the Hive PMC. But I'm happy to draft a
resolution for you and then let you call the vote. Should I do that?
Alan.
On Jan 11, 2013, at 4:34 PM, Carl Steinbach wrote:
> Hi Alan,
>
Sounds like a good plan to me. Since Ashutosh is a member of both the Hive
and HCatalog PMCs it probably makes more sense for him to call the vote,
but I'm willing to do it too.
On Wed, Jan 16, 2013 at 8:24 AM, Alan Gates wrote:
> If you think that's the best path forward that's fine. I can't c
I've created a wiki page for my proposed changes at
https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hive+Bylaws+for+Submodule+Committers
Text to be removed is struck through. Text to be added is in italics.
Any recommended changes before we vote?
Alan.
On Jan 17, 2013, a
Hi Alan,
Overall this looks good to me. I have a couple small suggestions:
* Replace occurrences of "Hive's subversion repository" with "Hive's
source code repository".
* In the "Actions" table the sentence "This also covers the creation of new
sub-projects within the project" should be changed
Changes made.
Alan.
On Jan 21, 2013, at 12:39 PM, Carl Steinbach wrote:
> Hi Alan,
>
> Overall this looks good to me. I have a couple small suggestions:
>
> * Replace occurrences of "Hive's subversion repository" with "Hive's
> source code repository".
> * In the "Actions" table the sentence
35 matches
Mail list logo
