[jira] [Created] (HADOOP-12111) Split test-patch off into its own TLP

2015-06-22 Thread Allen Wittenauer (JIRA)
Allen Wittenauer created HADOOP-12111: - Summary: Split test-patch off into its own TLP Key: HADOOP-12111 URL: https://issues.apache.org/jira/browse/HADOOP-12111 Project: Hadoop Common Iss

[jira] [Resolved] (HADOOP-12110) Consolidate usage of JSON libraries

2015-06-22 Thread Eric Yang (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang resolved HADOOP-12110. Resolution: Invalid Opened for the wrong project. Sorry, close as invalid. > Consolidate usage o

[jira] [Created] (HADOOP-12110) Consolidate usage of JSON libraries

2015-06-22 Thread Eric Yang (JIRA)
Eric Yang created HADOOP-12110: -- Summary: Consolidate usage of JSON libraries Key: HADOOP-12110 URL: https://issues.apache.org/jira/browse/HADOOP-12110 Project: Hadoop Common Issue Type: Bug

[jira] [Created] (HADOOP-12109) Distcp of file > 5GB to swift fails with HTTP 413 error

2015-06-22 Thread Phil D'Amore (JIRA)
Phil D'Amore created HADOOP-12109: - Summary: Distcp of file > 5GB to swift fails with HTTP 413 error Key: HADOOP-12109 URL: https://issues.apache.org/jira/browse/HADOOP-12109 Project: Hadoop Common

Re: [DISCUSS] project for pre-commit patch testing (was Re: upstream jenkins build broken?)

2015-06-22 Thread Andrew Purtell
On Mon, Jun 22, 2015 at 1:03 PM, Nick Dimiduk wrote: > On Mon, Jun 22, 2015 at 12:43 PM, Colin P. McCabe > wrote: > > > You mentioned that "most of our project will be focused on shell > > scripts" I guess based on the existing test-patch code. Allen did a > > lot of good work in this area rece

[jira] [Resolved] (HADOOP-12108) Erroneous behavior of use of wildcard character ( * ) in ls command of hdfs

2015-06-22 Thread Ravi Prakash (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash resolved HADOOP-12108. --- Resolution: Invalid Thanks Aman! Steve is right. You do need to use quotes when there is alr

Re: [DISCUSS] project for pre-commit patch testing (was Re: upstream jenkins build broken?)

2015-06-22 Thread Nick Dimiduk
On Mon, Jun 22, 2015 at 12:43 PM, Colin P. McCabe wrote: > You mentioned that "most of our project will be focused on shell > scripts" I guess based on the existing test-patch code. Allen did a > lot of good work in this area recently. I am curious if you evaluated > languages such as Python or

Re: [DISCUSS] More Maintenance Releases

2015-06-22 Thread Colin P. McCabe
+1 for creating a maintenance release with a more rapid release cadence and more effort put into stability backports. I think this would really be great for the project. Colin On Mon, Jun 22, 2015 at 2:43 AM, Akira AJISAKA wrote: > Hi everyone, > > In Hadoop Summit, I joined HDFS BoF and heard

Re: [DISCUSS] project for pre-commit patch testing (was Re: upstream jenkins build broken?)

2015-06-22 Thread Colin P. McCabe
+1 for making this a separate project. We've always struggled with a lot of forks of the test-patch code and perhaps this project can help create something that works well for multiple projects. Bypassing the incubator seems kind of weird (I didn't know that was an option) but I will let other pe

Re: [DISCUSS] More Maintenance Releases

2015-06-22 Thread Vinayakumar B
+1 for the idea of maintenance releases. Considering the amount code changes done in trunk and branch-2, cherry-picking may not be easy and straight forward in all issues. I would love to help in cherry-picking the fixes and reviewing them. I would also love to help in release process. Regards

Re: [DISCUSS] More Maintenance Releases

2015-06-22 Thread Allen Wittenauer
If 2.6 is the target, someone will have to verify that any cherry-picked patches actually work with JDK6 since the PMC voted to officially kill backward compatibility in a minor release. It’s going to be easier and probably smarter to fix 2.7 if that’s really desired. [1] Frank

Re: [DISCUSS] More Maintenance Releases

2015-06-22 Thread Karthik Kambatla
Thanks for starting this thread, Akira. +1 to more maintenance releases. More stable upstream releases avoids duplicating cherry-pick work across consumers/vendors, and shows the maturity of the project to users. I see value in backporting blocker/critical issues, but have mixed feelings about do

Re: [DISCUSS] More Maintenance Releases

2015-06-22 Thread Sean Busbey
More maintenance releases would be excellent. If y'all are going to make more releases on the 2.6 line, please consider backporting HADOOP-11710 as without it HBase is unusable on top of HDFS encryption. It's been inconvenient that the fix is only available in a non-production release line. -Sea

[jira] [Created] (HADOOP-12108) Erroneous behavior of use of wildcard character ( * ) in ls command of hdfs

2015-06-22 Thread Aman Goyal (JIRA)
Aman Goyal created HADOOP-12108: --- Summary: Erroneous behavior of use of wildcard character ( * ) in ls command of hdfs Key: HADOOP-12108 URL: https://issues.apache.org/jira/browse/HADOOP-12108 Project:

Re: [DISCUSS] More Maintenance Releases

2015-06-22 Thread Tsuyoshi Ozawa
Hi Akira, Thank you for starting interesting topic. +1 on the idea of More Maintenance Releases for old branches. It would be good if this activity is more coupled with Apache Yetus for users. BTW, I don't know one of committers, who is not PMC, can be a release manager. Does anyone know about th

[DISCUSS] More Maintenance Releases

2015-06-22 Thread Akira AJISAKA
Hi everyone, In Hadoop Summit, I joined HDFS BoF and heard from Jason Lowe that Apache Hadoop developers at Yahoo!, Twitter, and other non-distributors work very hard to maintenance Hadoop by cherry-picking patches to their own branches. I want to share the work with the community. If we can