Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards

2009-08-28 Thread Sanjay Radia
Hadoop 1.0's goal was compatibility on several fronts. (See https://issues.apache.org/jira/browse/HADOOP-5071) for details. Due to the amount of work involved, it has been necessary to split this work across several releases prior to 1.0. Turns out that release 0.21 has a number of Jiras ta

Re: Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards

2009-08-28 Thread Doug Cutting
Sanjay Radia wrote: I propose that we honor the compatibility of stable interfaces from release 0.21 onwards; i.e. apply the same post 1.0 rules to pre-1.0 releases. I think that makes 0.21 effectively 1.0. The hallmark of 1.0 will be our promise not to change APIs incompatibly until 2.0.

[Help] Why "java.util.zip.ZipOutputStream" need to use /tmp?

2009-08-28 Thread Steve Gao
would someone give us a hint? Thanks. Why "java.util.zip.ZipOutputStream" need to use /tmp? The hadoop version is 0.18.3 . Recently we got "out of space" issue. It's from "java.util.zip.ZipOutputStream". We found that /tmp is full and after cleaning /tmp the problem is solved. However why hadoop

Who are the gurus in Hive and/or Hbase?

2009-08-28 Thread Gopal Gandhi
We are inviting gurus or major contributors of Hive and/or Hbase (or anything related to Hadoop) to give us presentations about the products. Would you name a few names? The gurus must be in bay area. Thanks.

Re: Who are the major contributors to Hive and/or Hbase?

2009-08-28 Thread Gopal Gandhi
May be I should change the title? --- On Fri, 8/28/09, Gopal Gandhi wrote: From: Gopal Gandhi Subject: Who are the gurus in Hive and/or Hbase? To: common-u...@hadoop.apache.org, common-dev@hadoop.apache.org Cc: common-dev@hadoop.apache.org Date: Friday, August 28, 2009, 6:25 PM We are i

Re: Who are the major contributors to Hive and/or Hbase?

2009-08-28 Thread Gaurav Sharma
Hope this helps: http://hadoop.apache.org/hive/credits.html http://hadoop.apache.org/hbase/credits.html On Fri, Aug 28, 2009 at 1:26 PM, Gopal Gandhi wrote: > May be I should change the title? > > --- On Fri, 8/28/09, Gopal Gandhi wrote: > > > From: Gopal Gandhi > Subject: Who are the guru

Re: Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards

2009-08-28 Thread Sanjay Radia
On Aug 28, 2009, at 10:35 AM, Doug Cutting wrote: Sanjay Radia wrote: > I propose that we honor the compatibility of stable interfaces from > release 0.21 onwards; > i.e. apply the same post 1.0 rules to pre-1.0 releases. I think that makes 0.21 effectively 1.0. The hallmark of 1.0 will be o

Re: Towards Hadoop 1.0: Stronger API Compatibility from 0.21 onwards

2009-08-28 Thread Doug Cutting
Sanjay Radia wrote: No. The 1.0 proposal was that it included both API and wire compatibility. The proposal includes a lot of things, but it's so far just a proposal. There's been no vote to formally define what 1.0 will mean. In every discussion I've heard, from the very beginning of the p

[jira] Created: (HADOOP-6222) Core doesn't have TestCommonCLI facility

2009-08-28 Thread Boris Shkolnik (JIRA)
Core doesn't have TestCommonCLI facility Key: HADOOP-6222 URL: https://issues.apache.org/jira/browse/HADOOP-6222 Project: Hadoop Common Issue Type: Test Reporter: Boris Shkolnik TestCLI

[VOTE] Should we release Common 0.20.1-rc0?

2009-08-28 Thread Owen O'Malley
I've rolled a release candidate for 0.20.1. Please try the release and vote on whether we should release it. http://people.apache.org/~omalley/hadoop-0.20.1-rc0 -- Owen

Re: [VOTE] Should we release Common 0.20.1-rc0?

2009-08-28 Thread Todd Lipcon
Hey Owen, Looks like it might need a chmod: > You don't have permission to access /~omalley/hadoop-0.20.1-rc0/hadoop-0.20.1.tar.gz on this server. -Todd On Fri, Aug 28, 2009 at 5:06 PM, Owen O'Malley wrote: > I've rolled a release candidate for 0.20.1. Please try the release and vote > on whe

Re: Weird 'java.io.IOException: Task process exit with nonzero status of 134' problem

2009-08-28 Thread indoos
Hi, Todd, right on target!! Tony, heap usage would be at least 30% extra in 64 bit as compared to 32 bit. Increasing the SWAP size might help in bypassing the out of memory error, but does impact processing speed. Todd is referring using -XX:+UseCompressedOops option. You might have to find if y