On Wed, Apr 21, 2010 at 10:35 PM, Jeff Hammerbacher ham...@cloudera.comwrote:
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,
What is the advantage of becoming a TLP to the project itself? I have heard
that it is something that apache wants, but considering that we are very
comfortable on how Hive interacts with the Hadoop ecosystem as a sub project
for Hadoop, there has to be some big incentive for the project to be
I am definitely against moving Hive out of Hadoop. There is appreciable
representation of Hive inside the Hadoop PMC and, as far as I can say, there
is no additional burden on the Hadooo PMC to make Hive remain inside Hadoop.
I respect Jeff/Amr's comments on their viewpoints, but I beg to differ
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 zsh...@gmail.com wrote:
As a Hive committer, I don't feel
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, one
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
