[jira] [Created] (HADOOP-11871) Improve RSRawErasureDecoder avoiding unnecessary compuating and recovering

Kai Zheng created HADOOP-11871: -- Summary: Improve RSRawErasureDecoder avoiding unnecessary compuating and recovering Key: HADOOP-11871 URL: https://issues.apache.org/jira/browse/HADOOP-11871 Project: Had

[jira] [Created] (HADOOP-11870) [JDK8] AuthenticationFilter, CertificateUtil, SignerSecretProviders, KeyAuthorizationKeyProvider Javadoc issues

Robert Kanter created HADOOP-11870: -- Summary: [JDK8] AuthenticationFilter, CertificateUtil, SignerSecretProviders, KeyAuthorizationKeyProvider Javadoc issues Key: HADOOP-11870 URL: https://issues.apache.org/jira/

[jira] [Created] (HADOOP-11869) checkstyle rules/script need re-visiting

Sidharta Seethana created HADOOP-11869: -- Summary: checkstyle rules/script need re-visiting Key: HADOOP-11869 URL: https://issues.apache.org/jira/browse/HADOOP-11869 Project: Hadoop Common

Re: [RESULT][VOTE] Release Apache Hadoop 2.7.0 RC0

It took a while for the artifact distribution to come around, I initially had trouble pushing them from home too. Anyways, I just updated the website too. Sending an announcement now.. Thanks, +Vinod On Apr 20, 2015, at 8:06 PM, Vinod Kumar Vavilapalli wrote: > With 22 +1s (7 binding), one +

Re: Set minimum version of Hadoop 3 to JDK 8

You're absolutely right Steve. We should get the jobs under control. At the very least, before we move to JDK 8 in Jenkins, we should get the Java8 nightly builds working. I didn't realize we had these, and I had thought all compiling and most test issues with JDK8 were already fixed based on wh

RE: IMPORTANT: testing patches for branches

Hi Allen, This sounds great. >> Naming a patch foo-HDFS-7285.00.patch should get tested on the HDFS-7285 >> branch. Does it happen locally in developer's machine when running test-patch.sh, or also mean something in Hadoop Jenkins building when a JIRA becoming patch available? Thanks. Regard

Re: IMPORTANT: testing patches for branches

Perhaps a script is due that creates the patch file with -exactly- the right name. Something like what HBase has as dev-support/make_patch.sh perhaps? On Wed, Apr 22, 2015 at 10:30 PM, Allen Wittenauer wrote: > > Oh, this is also in the release notes, but one can use a git reference # > as well.

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

Approach (1) seems like a good way to handle stability concerns people might have. If we explicitly distinguish between current and stable (i.e., not set them both to the latest release). It would be nice to do a VOTE for calling a release stable. I would use approach (2) for compatibility concern

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

Thanks for forking this Vinod, Linux used to do the odd/even minor versions for unstable/stable, but that went away when 2.6 lasted forever. With the 3.x and 4.x I think it's just always stable. The odd/even though was at least a convention everyone knew about. Stack can comment better than I abo

[DISCUSS] Release numbering for stable 2.8 and beyond

Forking the thread. In the previous 2.7.1 thread [1], there were enough yays to my proposal to wait for a bug-fix release or two before calling a 2.x release stable. There were some concerns about the naming. We have two options, taking 2.8 as an example (1) Release 2.8.0, call it as an alpha

Re: [DISCUSS] Looking to a 2.8.0 release

+dev lists. Forgot about that, sure. I added this and my initial list to the Roadmap wiki. Thank +Vinod On Apr 21, 2015, at 9:34 PM, Rohith Sharma K S wrote: > Dear Vinod > > Regarding the road map of Hadoop-2.8.0, Can basic Application priority > working model includes in next releas

Re: IMPORTANT: testing patches for branches

Oh, this is also in the release notes, but one can use a git reference # as well. :) (with kudos to OOM for the idea.) On Apr 22, 2015, at 8:57 PM, Allen Wittenauer wrote: > > More than likely. It probably needs more testing (esp under Jenkins). > > It should be noted that the code in test

Re: IMPORTANT: testing patches for branches

More than likely. It probably needs more testing (esp under Jenkins). It should be noted that the code in test-patch.sh has lots of problems with branch-0, minor, and micro releases. But for major releases, it seems to work well for me. :) On Apr 22, 2015, at 8:45 PM, Vinod Kumar Vavilapa

Re: IMPORTANT: testing patches for branches

Does this mean HADOOP-7435 is no longer needed / closeable as dup? Thanks +Vinod On Apr 22, 2015, at 12:34 PM, Allen Wittenauer wrote: > > Hey gang, > > Just so everyone is aware, if you are working on a patch for either a > feature branch or a major branch, if you name the patc

IMPORTANT: testing patches for branches

Hey gang, Just so everyone is aware, if you are working on a patch for either a feature branch or a major branch, if you name the patch with the branch name following the spec in HowToContribute (and a few other ways… test-patch tries to figure it out!), test-patch.sh *should*

[jira] [Created] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

Gopal V created HADOOP-11867: Summary: FS API: Add a high-performance vectored Read to FSDataInputStream API Key: HADOOP-11867 URL: https://issues.apache.org/jira/browse/HADOOP-11867 Project: Hadoop Commo

[jira] [Created] (HADOOP-11866) increase readability of the white space script

Naganarasimha G R created HADOOP-11866: -- Summary: increase readability of the white space script Key: HADOOP-11866 URL: https://issues.apache.org/jira/browse/HADOOP-11866 Project: Hadoop Common

Re: committing HADOOP-11746 test-patch improvements

On Wed, Apr 22, 2015 at 2:10 AM, Allen Wittenauer wrote: > > > * There have been a few runs which seems to indicate that *something* is > destroying the artifact directory in the middle of runs…. which is very > very odd and something I hadn’t seen in any of my testing. In any case, I > clearly

[jira] [Created] (HADOOP-11865) Incorrect path mentioned in document for accessing script files

J.Andreina created HADOOP-11865: --- Summary: Incorrect path mentioned in document for accessing script files Key: HADOOP-11865 URL: https://issues.apache.org/jira/browse/HADOOP-11865 Project: Hadoop Commo

Re: Set minimum version of Hadoop 3 to JDK 8

> On 21 Apr 2015, at 23:31, Andrew Wang wrote: > > Hey Robert, > > As a first step, could we try switching all our precommit and nightly > builds over to use 1.8? This is a prerequisite for HADOOP-11858, and safe > to do in any case since it'll still target 1.7. +1 we have jenkin builds runni

[jira] [Created] (HADOOP-11864) JWTRedirectAuthenticationHandler breaks java8 javadocs

Steve Loughran created HADOOP-11864: --- Summary: JWTRedirectAuthenticationHandler breaks java8 javadocs Key: HADOOP-11864 URL: https://issues.apache.org/jira/browse/HADOOP-11864 Project: Hadoop Common

Build failed in Jenkins: Hadoop-common-trunk-Java8 #173

See Changes: [vinayakumarb] HDFS-7993. Provide each Replica details in fsck (Contributed by J.Andreina) [arp] HDFS-8163. Using monotonicNow for block report scheduling causes test failures on recently restarted systems. (Arp

Re: Which newbie Jira's need work?

Hi Darrell, Thank you for having interest for contributions to Hadoop project! > * How do I know if a newbie Jira is even still valid? Please ping committers whether the issue is valid when the issue looks to have been resolved already. > * Does anybody have any suggestions for a suitable newbi

Which newbie Jira's need work?

Hi All, First off I've submitted a patch for HADOOP-11813 as a starter for 10, this was an easy change and starts to get me familiar with where things are. Now I've been looking through the newbie Jira's to see what else I can do to help, but I'm struggling to see the wood for the trees, which I

Re: committing HADOOP-11746 test-patch improvements

Err, first jira mentioned should be HADOOP-11861. On Apr 22, 2015, at 8:10 AM, Allen Wittenauer wrote: > > Some status: > > * So far, HADOOP-11627 was filed which is luckily an extremely easy bug to > fix. > > * There have been a few runs which seems to indicate that *something* is > destr

Re: committing HADOOP-11746 test-patch improvements

Some status: * So far, HADOOP-11627 was filed which is luckily an extremely easy bug to fix. * There have been a few runs which seems to indicate that *something* is destroying the artifact directory in the middle of runs…. which is very very odd and something I hadn’t seen in any of my testi