[jira] [Created] (HADOOP-11510) Expose truncate API via FileContext

Yi Liu created HADOOP-11510: --- Summary: Expose truncate API via FileContext Key: HADOOP-11510 URL: https://issues.apache.org/jira/browse/HADOOP-11510 Project: Hadoop Common Issue Type: New Feature

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #87

See

Jenkins build is back to normal : Hadoop-Common-trunk #1387

See

Can someone review: HADOOP-6221

A six years ago I filed a patch HADOOP-6221 , RPC Client operations cannot be interrupted https://issues.apache.org/jira/browse/HADOOP-6221 The latest patch is in sync with trunk. Could someone take a look? -Steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the i

permissions to write in wiki

Hi, I'd like to add fnews.com on the list of sites powered by Hadoop on the wiki page @ https://wiki.apache.org/hadoop/PoweredBy Can I get write permission to this page for my username DavidTing so that I can add the entry myself? Cheers, David

Wiki permissions!

Hi folks! Could you please give me write priviledges to https://wiki.apache.org/hadoop/Distributions%20and%20Commercial%20Support ? ThanksRavi

[jira] [Created] (HADOOP-11511) Add RackAwareness to the web side bar

Allen Wittenauer created HADOOP-11511: - Summary: Add RackAwareness to the web side bar Key: HADOOP-11511 URL: https://issues.apache.org/jira/browse/HADOOP-11511 Project: Hadoop Common Iss

Re: Patch review process

Let's move this over to common-dev@, general@ is normally used for project announcements rather than discussion topics. I'd like to summarize a few things mentioned on the private@ thread, related to streamlining the code submission process. - Gerrit was brought up again, as it has in the past, a

Re: Patch review process

I'm moving this all to common-dev@ as general is more where announcements go than anything else. I think too many patches are falling by the wayside. It takes a lot of time and effort to get patches in, small patches that aren't viewed as critical tend to atrophy: lost in "patch-availalble" state,

Re: Patch review process

IMO the number one improvement would be a web-based review tool. We could evaluate Atlassian Crucible since it claims to integrate well with Jira. I have not tried https://reviews.apache.org/r/new/. Some easy improvements that were also raised by others on the private list: - Encourage contributor

Re: Patch review process

reviews.apache.org is backed by Review Board, and I've had a very positive experience with that tool on other projects. HADOOP-9629 is a Hadoop patch where we decided to go ahead and use it, and I think it helped. AFAIK, there is no rule against using it in Hadoop, but it does have the side effec

Re: Patch review process

Thanks for that data point Chris. It looks like reviews.apache.org no longer works. hadoop-hdfs-git may be pointing to an outdated repository. I'll file a ticket with Infra. On Mon, Jan 26, 2015 at 2:41 PM, Chris Nauroth wrote: > reviews.apache.org is backed by Review Board, and I've had a very

Re: Patch review process

Just out of left field: Since we already migrated to git (Thanks everyone for that effort) should we try using github's UI? Isn't that how the majority of the rest of the world started doing code reviews? On Monday, January 26, 2015 3:57 PM, Arpit Agarwal wrote: Thanks for that da

Re: Patch review process

I think someone mentioned this earlier - the concern was keeping the review comments searchable from one location, ideally within Jira. On Mon, Jan 26, 2015 at 5:52 PM, Ravi Prakash wrote: > Just out of left field: Since we already migrated to git (Thanks everyone > for that effort) should we t

Re: Patch review process

As popular as the github workflow is, there are some things I'm not a big fan of. For one, the review tends to cause a flurry of separate notifications as opposed to a single atomic set of comments. On Mon, Jan 26, 2015 at 6:17 PM, Arpit Agarwal wrote: > I think someone mentioned this earlier -