Re: [VOTE] - Release 2.0.5-beta

2013-05-21 Thread sanjay Radia
+1 on 2.0.5 defined in this thread with the new features. But I am supportive of an earlier release that has ALL the compatibility changes, without the features. sanjay On May 15, 2013, at 10:57 AM, Arun C Murthy wrote: Folks, ... I propose we continue the original plan and make a

Re: [VOTE] - Release 2.0.5-beta

2013-05-21 Thread Konstantin Shvachko
-1 for the record. This is a great plan for 2.1, which I would gladly support, but not for 2.0.5. I do not see how the previous vote could have been confusing, as it contained a direct quotation of the relative clause of Bylaws. Arun, the format of this vote remains confusing. What is the

Re: [VOTE] - Release 2.0.5-beta

2013-05-21 Thread Konstantin Shvachko
Chris, I find you are contradicting yourself within this message and with some other of yours. But I want to address only one thing here This has exposed a bug in our bylaws, which we can fix. This could be a bug, and we may need to fix it. But until then it is a bylaw, which is the only rule

[jira] [Created] (HADOOP-9583) test-patch gives +1 despite build failure when running tests

2013-05-21 Thread Jason Lowe (JIRA)
Jason Lowe created HADOOP-9583: -- Summary: test-patch gives +1 despite build failure when running tests Key: HADOOP-9583 URL: https://issues.apache.org/jira/browse/HADOOP-9583 Project: Hadoop Common

Where should we host Hadoop FileSystem plugins for 3rd Party FileSystems?

2013-05-21 Thread Stephen Watt
Hi Folks My name is Steve Watt and I am presently working on enabling glusterfs to be used as a Hadoop FileSystem. Most of the work thus far has involved developing a Hadoop FileSystem plugin for glusterfs. I'm getting to the point where the plugin is becoming stable and I've been trying to

[jira] [Created] (HADOOP-9584) fix findbugs warnings

2013-05-21 Thread Giridharan Kesavan (JIRA)
Giridharan Kesavan created HADOOP-9584: -- Summary: fix findbugs warnings Key: HADOOP-9584 URL: https://issues.apache.org/jira/browse/HADOOP-9584 Project: Hadoop Common Issue Type: Bug

[jira] [Created] (HADOOP-9585) unit test failure :org.apache.hadoop.fs.TestFsShellReturnCode.testChgrp

2013-05-21 Thread Giridharan Kesavan (JIRA)
Giridharan Kesavan created HADOOP-9585: -- Summary: unit test failure :org.apache.hadoop.fs.TestFsShellReturnCode.testChgrp Key: HADOOP-9585 URL: https://issues.apache.org/jira/browse/HADOOP-9585

[jira] [Created] (HADOOP-9586) unit test failure: org.apache.hadoop.hdfs.TestFileCreation.testFileCreationSetLocalInterface

2013-05-21 Thread Giridharan Kesavan (JIRA)
Giridharan Kesavan created HADOOP-9586: -- Summary: unit test failure: org.apache.hadoop.hdfs.TestFileCreation.testFileCreationSetLocalInterface Key: HADOOP-9586 URL:

[jira] [Created] (HADOOP-9587) unit test failure: org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup.testBalancerWithRackLocality

2013-05-21 Thread Giridharan Kesavan (JIRA)
Giridharan Kesavan created HADOOP-9587: -- Summary: unit test failure: org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup.testBalancerWithRackLocality Key: HADOOP-9587 URL:

Re: [VOTE] - Release 2.0.5-beta

2013-05-21 Thread Matt Foley
I've now started a separate discussion thread in common-dev@, titled [PROPOSAL] change in bylaws to remove Release Plan vote. If it achieves consensus, I'll put it to a vote to so change the bylaws. Best, --Matt On Sat, May 18, 2013 at 4:22 PM, Chris Douglas cdoug...@apache.org wrote: The

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Mattmann, Chris A (398J)
+1million I completely agree with Chris D's separate email too about not vote'ing about intentions, and voting on actual artifacts. The fact of the matter at the ASF is that any PMC member; heck any contributor can roll a release candidate. If that candidate receives at least 3 PMC member +1s

[jira] [Created] (HADOOP-9589) Extra master key is created when AbstractDelegationTokenSecretManager is started

2013-05-21 Thread Jian He (JIRA)
Jian He created HADOOP-9589: --- Summary: Extra master key is created when AbstractDelegationTokenSecretManager is started Key: HADOOP-9589 URL: https://issues.apache.org/jira/browse/HADOOP-9589 Project:

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Chris Douglas
+1 Thanks for taking care of this, Matt. -C On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition in the dev community that any committer can create a

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Aaron T. Myers
+1 I've always found the Release Plan votes a bit bizarre, and the fact that we've gone through many releases that did not have a corresponding Release Plan vote suggest to me that we should just scrap them. -- Aaron T. Myers Software Engineer, Cloudera On Tue, May 21, 2013 at 5:37 PM, Chris

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Suresh Srinivas
+1 On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition in the dev community that any committer can create a branch, and propose release candidates from

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Alejandro Abdelnur
+1 On Tue, May 21, 2013 at 2:48 PM, Suresh Srinivas sur...@hortonworks.comwrote: +1 On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition in the

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Giridharan Kesavan
+1 -Giri On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition in the dev community that any committer can create a branch, and propose release

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Arpit Gupta
+1 -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On May 21, 2013, at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition in the dev community that any committer can

RE: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Jagane Sundar
I see one significant benefit to having Release Plan votes: Fewer releases with more members of the community working on any given release. In turn, fewer Hadoop releases implies less confusion for end users attempting to download and use an Apache Hadoop release. If there are a dozen different

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Arun C Murthy
+1, thanks for taking the initiative on this Matt. On May 21, 2013, at 2:10 PM, Matt Foley wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition in the dev community that any committer can create a branch, and

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Eli Collins
+1 thanks Matt. On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition in the dev community that any committer can create a branch, and propose release

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Sandy Ryza
+1 (non-binding) On Tue, May 21, 2013 at 4:02 PM, Eli Collins e...@cloudera.com wrote: +1 thanks Matt. On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Jitendra Pandey
+1 On Tue, May 21, 2013 at 4:02 PM, Eli Collins e...@cloudera.com wrote: +1 thanks Matt. On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Karthik Kambatla
+1 (non-binding) On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey jiten...@hortonworks.comwrote: +1 On Tue, May 21, 2013 at 4:02 PM, Eli Collins e...@cloudera.com wrote: +1 thanks Matt. On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Mahadev Konar
+1. thanks mahadev On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla ka...@cloudera.com wrote: +1 (non-binding) On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey jiten...@hortonworks.comwrote: +1 On Tue, May 21, 2013 at 4:02 PM, Eli Collins e...@cloudera.com wrote: +1 thanks Matt.

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Matt Foley
13/14 +1's. I think that constitutes consensus. Moving this to a VOTE thread. Please repeat your +1s :-) Cheers, --Matt On Tue, May 21, 2013 at 5:33 PM, Mahadev Konar maha...@hortonworks.comwrote: +1. thanks mahadev On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla ka...@cloudera.com

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Mattmann, Chris A (398J)
Why repeat just tally new ones? Sent from my iPhone On May 21, 2013, at 6:58 PM, Matt Foley ma...@apache.org wrote: 13/14 +1's. I think that constitutes consensus. Moving this to a VOTE thread. Please repeat your +1s :-) Cheers, --Matt On Tue, May 21, 2013 at 5:33 PM, Mahadev Konar

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Matt Foley
Ok, if no one complains I will phrase the vote to include +1's explicitly cast in the discussion thread. --Matt On Tue, May 21, 2013 at 6:58 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Why repeat just tally new ones? Sent from my iPhone On May 21, 2013, at 6:58 PM,

[VOTE] change in bylaws to remove Release Plan vote

2013-05-21 Thread Matt Foley
This was previously discussed in the thread [PROPOSAL] change in bylaws to remove Release Plan vote. 13 people explicitly cast +1s in that thread. Absent objection I will count those as votes without requiring them to (re-)respond to this VOTE thread. The following change is proposed in the

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

2013-05-21 Thread Matt Foley
Hi Jagane, since you did not explicitly cast a -1 or other numerical vote, please if you wish go ahead and cast a vote in the VOTE thread. Best regards, --Matt On Tue, May 21, 2013 at 3:47 PM, Jagane Sundar jag...@sundar.org wrote: I see one significant benefit to having Release Plan votes:

Re: [VOTE] change in bylaws to remove Release Plan vote

2013-05-21 Thread Hitesh Shah
+1. -- Hitesh On May 21, 2013, at 7:03 PM, Matt Foley wrote: This was previously discussed in the thread [PROPOSAL] change in bylaws to remove Release Plan vote. 13 people explicitly cast +1s in that thread. Absent objection I will count those as votes without requiring them to

[jira] [Created] (HADOOP-9590) Move to JDK7 improved APIs for file operations when available

2013-05-21 Thread Ivan Mitic (JIRA)
Ivan Mitic created HADOOP-9590: -- Summary: Move to JDK7 improved APIs for file operations when available Key: HADOOP-9590 URL: https://issues.apache.org/jira/browse/HADOOP-9590 Project: Hadoop Common

[jira] [Created] (HADOOP-9591) Hadoop SnappyCodec (incorrectly?) uses block compression

2013-05-21 Thread Uri Laserson (JIRA)
Uri Laserson created HADOOP-9591: Summary: Hadoop SnappyCodec (incorrectly?) uses block compression Key: HADOOP-9591 URL: https://issues.apache.org/jira/browse/HADOOP-9591 Project: Hadoop Common