Build failed in Jenkins: Hadoop-Common-trunk #803

2013-06-18 Thread Apache Jenkins Server
See Changes: [vinodkv] YARN-846. Move pb Impl classes from yarn-api to yarn-common. Contributed by Jian He. [acmurthy] YARN-799. Fix CgroupsLCEResourcesHandler to use /tasks instead of /cgroup.procs. Contributed by Chris Riccomin

[jira] [Created] (HADOOP-9651) Filesystems to throw FileAlreadyExistsException in createFile(path, overwrite=false) when the file exists

2013-06-18 Thread Steve Loughran (JIRA)
Steve Loughran created HADOOP-9651: -- Summary: Filesystems to throw FileAlreadyExistsException in createFile(path, overwrite=false) when the file exists Key: HADOOP-9651 URL: https://issues.apache.org/jira/browse/

Hadoop 2.0 - org.apache.hadoop.fs.Hdfs vs. DistributedFileSystem?

2013-06-18 Thread Stephen Watt
Hi Folks My understanding is that from Hadoop 2.0 onwards the AbstractFileSystem is now the strategic class to extend for writing Hadoop FileSystem plugins. This is a departure from previous versions where one would extend the FileSystem class. This seems to be reinforced by the hadoop-default.

Re: Hadoop 2.0 - org.apache.hadoop.fs.Hdfs vs. DistributedFileSystem?

2013-06-18 Thread Eli Collins
Hey Steve, That's correct, see HADOOP-6223 for the history. However, per Andrew I don't think it's realistic to expect people to migrate off FileSystem for a while (I filed HADOOP-6446 well over three years ago). The unfortunate consequence of the earlier decision to have parallel interfaces rat

[jira] [Created] (HADOOP-9652) FileContext#getFileLinkStatus does not fill in the link owner and mode

2013-06-18 Thread Colin Patrick McCabe (JIRA)
Colin Patrick McCabe created HADOOP-9652: Summary: FileContext#getFileLinkStatus does not fill in the link owner and mode Key: HADOOP-9652 URL: https://issues.apache.org/jira/browse/HADOOP-9652

Re: Heads up: branch-2.1-beta

2013-06-18 Thread Arun C Murthy
Ping. Any luck? On Jun 17, 2013, at 4:06 PM, Roman Shaposhnik wrote: > On Sun, Jun 16, 2013 at 5:14 PM, Arun C Murthy wrote: >> Roman, >> >> Is there a chance you can run the tests with the full stack built against >> branch-2.1-beta and help us know where we are? > > I will try to kick off