___
> From: Jeff Hammerbacher [mailto:ham...@cloudera.com]
> Sent: Wednesday, April 21, 2010 7:35 PM
> To: hive-dev@hadoop.apache.org
> Cc: Ashish Thusoo
> Subject: Re: [DISCUSSION] To be (or not to be) a TLP - that is the question
>
> Hive already does the work to
(or not to be) a TLP - that is the question
Hive already does the work to run on multiple versions of Hadoop, and the
release cycle is independent of Hadoop's. I don't see why it should remain a
subproject. I'm +1 on Hive becoming a TLP.
On Tue, Apr 20, 2010 at 2:03 PM, Zheng S
On Wed, Apr 21, 2010 at 10:35 PM, Jeff Hammerbacher wrote:
> Hive already does the work to run on multiple versions of Hadoop, and the
> release cycle is independent of Hadoop's. I don't see why it should remain
> a
> subproject. I'm +1 on Hive becoming a TLP.
>
> On Tue, Apr 20, 2010 at 2:03 PM,
Hive already does the work to run on multiple versions of Hadoop, and the
release cycle is independent of Hadoop's. I don't see why it should remain a
subproject. I'm +1 on Hive becoming a TLP.
On Tue, Apr 20, 2010 at 2:03 PM, Zheng Shao wrote:
> As a Hive committer, I don't feel the benefit we
As a Hive committer, I don't feel the benefit we get from becoming a
TLP is big enough (compared with the cost) to make Hive a TLP.
>From Chris's comment I see that the cost is not that big, but I still
wonder what benefit we will get from that.
Also I didn't get the idea of the joke ("In fact, on
I am personally +1 on Hive being a TLP, I think it did reach the
community adoption and maturity level required for that. In fact, one
could argue that Pig opting not to be TLP yet is why Hive should go TLP
:) (jk).
The real question to ask is whether there is a volunteer to take care of
the
Hi Folks,
Recently Apache Board asked the Hadoop PMC if some sub projects can become top
level projects. In the opinion of the board, big umbrella projects make it
difficult to monitor the health of the communities within the sub projects. If
Hive does become a TLP, then we would have to elect
