Re: state of HOD

Hi Chris, HOD is end-of-life starting with Hadoop 0.20. It was active while Python 2.5 was in use. I don't know of anyone who used with more recent versions of python. Also it isn't tested with later versions of Hadoop. Starting 2.0, Hadoop itself has resource management built in as part of the s

Re: Hadoop datajoin package

It is an application for data join. May be we should put it in examples where it is more discoverable? And then we can migrate it to new API in a follow up. +Vinod On Mon, Jan 14, 2013 at 6:14 AM, Hemanth Yamijala wrote: > On the user list, there was a question about the Hadoop datajoin packa

Re: Release numbering for branch-2 releases

On Tue, Jan 29, 2013 at 12:56 PM, Arun C Murthy wrote: > Folks, > > There has been some discussions about incompatible changes in the > hadoop-2.x.x-alpha releases on HADOOP-9070, HADOOP-9151, HADOOP-9192 and > few other jiras. Frankly, I'm surprised about some of them since the > 'alpha' monike

[jira] [Created] (HADOOP-9267) hadoop -help, -h, --help should show usage instructions

Andrew Wang created HADOOP-9267: --- Summary: hadoop -help, -h, --help should show usage instructions Key: HADOOP-9267 URL: https://issues.apache.org/jira/browse/HADOOP-9267 Project: Hadoop Common

Re: Release numbering for branch-2 releases

The discussions in HADOOP-9151 were related to wire-compatibility. I think we all agree that breaking API compatibility is not allowed without deprecating them first in a prior major release - this is something we have followed since hadoop-0.1. I agree we need to spell out what changes we can

Re: Release numbering for branch-2 releases

Thanks for bringing this up Arun. One of the issues is that we haven't been clear about what type of compatibility breakages are allowed, and which are not. For example, renaming FileSystem#open is incompatible, and not OK, regardless of the alpha/beta tag. Breaking a server/server APIs is OK pr

Re: Release numbering for branch-2 releases

I still have a list of pending API/protocol cleanup in YARN that need to be in before we even attempt supporting compatibility further down the road. There's no way we can support wire compatibility with the APIs in the state that they are in now. So, +1 for a beta sometime in March. There are som

[jira] [Created] (HADOOP-9266) correct release audit warnings on branch-trunk-win

Chris Nauroth created HADOOP-9266: - Summary: correct release audit warnings on branch-trunk-win Key: HADOOP-9266 URL: https://issues.apache.org/jira/browse/HADOOP-9266 Project: Hadoop Common

[jira] [Created] (HADOOP-9265) S3 blockstore filesystem breaks part of the Filesystem contract

Steve Loughran created HADOOP-9265: -- Summary: S3 blockstore filesystem breaks part of the Filesystem contract Key: HADOOP-9265 URL: https://issues.apache.org/jira/browse/HADOOP-9265 Project: Hadoop C

[jira] [Created] (HADOOP-9264) port change to use Java untar API on Windows from branch-1-win to trunk

Chris Nauroth created HADOOP-9264: - Summary: port change to use Java untar API on Windows from branch-1-win to trunk Key: HADOOP-9264 URL: https://issues.apache.org/jira/browse/HADOOP-9264 Project: Ha

[jira] [Created] (HADOOP-9263) findbugs reports extra warnings on branch-1

Chris Nauroth created HADOOP-9263: - Summary: findbugs reports extra warnings on branch-1 Key: HADOOP-9263 URL: https://issues.apache.org/jira/browse/HADOOP-9263 Project: Hadoop Common Issue T

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

See