[VOTE] Release Apache Hadoop 2.0.5-alpha (rc1)

All, I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I would like to release. This is a stabilization release that includes fixed for a couple a of issues discovered in the testing with BigTop 0.6.0 release candidate. The RC is available at: http://people.apache.org/~cos/had

[jira] [Reopened] (HDFS-3498) Make Replica Removal Policy pluggable and ReplicaPlacementPolicyDefault extensible for reusing code in subclass

[ https://issues.apache.org/jira/browse/HDFS-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reopened HDFS-3498: -- Reopen jira for backport to branch-2 > Make Replica Removal Policy pluggable and ReplicaPla

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

Ok, WRT HDFS-4646 - it is all legit and the code is in branch-2.0.4-alpha and later. It has been committed as r1465124 The reason it isn't normally visible because of the weird commit message: svn merge -c1465121 from trunk So, we good. I am done with the CHANGES.txt fixed that

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

Alejandro, thanks for looking into this. Indeed - I missed the 2.0.5-alpha section in YARN CHANGES.txt. Added now. As for HDFS-4646: apparently I didn't get into to branch-2.0.4-alpha back then, although I distinctively remember doing this. Let me pull it into 2.0.5-alpha and update CHANGES.txt to

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

2.1.0-alpha is 2.0.5-beta actually. --Send from my Sony mobile. On Jun 1, 2013 8:14 AM, "Ted Yu" wrote: > I am currently testing HBase 0.95 using 2.0.5-SNAPSHOT artifacts. > > Would 2.1.0-SNAPSHOT maven artifacts be available after tomorrow's change ? > > Thanks > > On Fri, May 31, 2013 at 12:45

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

Verified MD5 & signature, built, configured pseudo cluster, run a couple of sample jobs, tested HTTPFS. Still, something seems odd. The HDFS CHANGES.txt has the following entry under 2.0.5-alpha: HDFS-4646. createNNProxyWithClientProtocol ignores configured timeout value (Jagane Sundar via cos

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

I am currently testing HBase 0.95 using 2.0.5-SNAPSHOT artifacts. Would 2.1.0-SNAPSHOT maven artifacts be available after tomorrow's change ? Thanks On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik wrote: > Guys, > > I will be performing some changes wrt to moving 2.0.4.1 release candidate

[VOTE] Release Apache Hadoop 2.0.5-alpha

All, I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I would like to release. This is a stabilization release that includes fixed for a couple a of issues discovered in the testing with BigTop 0.6.0 release candidate. The RC is available at: http://people.apache.org/~cos/had

Re: Backwards compatibility of FileSystem interface.

(forwarding to common-dev which is where this discussion about APIs should go) 1. FileSystem API may add new methods from version to version. There's some list operation that's gone in too. 2. I don't think there are any guarantees that we don't add new methods to a base class -it's w

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

Indeed! The second part is happening on Saturday, JUN01 2013 1PM-2PM PST. On Fri, May 31, 2013 at 01:01PM, Alejandro Abdelnur wrote: > Cos, just to be clear, this is happening SAT JUN01 1PM-2PM PST, not now > (FRI MAY31 1PM PST). Correct? > > Thx > > On Fri, May 31, 2013 at 12:45 PM, Konstantin

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

Cos, just to be clear, this is happening SAT JUN01 1PM-2PM PST, not now (FRI MAY31 1PM PST). Correct? Thx On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik wrote: > Guys, > > I will be performing some changes wrt to moving 2.0.4.1 release candidate > to > 2.0.5 space. As outline below by Ale

Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

Guys, I will be performing some changes wrt to moving 2.0.4.1 release candidate to 2.0.5 space. As outline below by Alejandro: 1. I will create new 2.0.5-alpha branch from the current head of 2.0.4-alpha that contains 2.0.4.1 changes 2. consequently, set the artifacts version on the new branch to

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

Thanks for the headstart Arun! I will be sending a separate email to the *-dev@ lists outlining the plan and the schedule of the changes, so we won't step on each other feet, like Vinod expressed earlier. Cos On Fri, May 31, 2013 at 11:20AM, Arun C Murthy wrote: > > On May 30, 2013, at 8:41 PM,

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On May 30, 2013, at 8:41 PM, Alejandro Abdelnur wrote: > Konstantin, Cos, > > As we change from 2.0.4.1 to 2.0.5 you'll need to do the following > housekeeping as you work the new RC. > > * rename the svn branch > * update the versions in the POMs > * update the CHANGES.txt in trunk, branch-2 a

[jira] [Created] (HDFS-4869) FsShell get command does not support writing to stdout

Cristina L. Abad created HDFS-4869: -- Summary: FsShell get command does not support writing to stdout Key: HDFS-4869 URL: https://issues.apache.org/jira/browse/HDFS-4869 Project: Hadoop HDFS

Re: Backwards compatibility of FileSystem interface.

For context - It appears that over time the FileSystem has changed the signature to the "createNonRecursive" method, (in 2.x there are 3 signatures, in 1.x, there are 2 signatures). [root@jvyas hadoop-common]# git checkout branch-1.1 Switched to branch 'branch-1.1' [root@jvyas hadoop-common]# grep

Build failed in Jenkins: Hadoop-Hdfs-trunk #1416

See Changes: [cdouglas] MAPREDUCE-5176. Add annotation for tagging tasks as responsive to preemption. Contributed by Carlo Curino, cdouglas [szetszwo] Move snapshot JIRAs to 2.0.5 section in CHANGES.txt. [sseth] MAPREDUCE-5286. Chan

Hadoop-Hdfs-trunk - Build # 1416 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1416/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 14517 lines...] [INFO] --- maven-source-plugin:2.1.2:test

Re: Backwards compatibility of FileSystem interface.

Jay, this is is more a common-dev question, as it goes beyond hdfs On 31 May 2013 02:07, Jay Vyas wrote: > Hi : > > Are FileSystem interfaces gauranteed to retain semantics of the old > FileSystem contract? > retain the explicit semantics, yes. Implementations may change some implementation det