[jira] [Resolved] (HADOOP-9597) FileSystem open() API is not clear if FileNotFoundException is throw when the path does not exist

[ https://issues.apache.org/jira/browse/HADOOP-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HADOOP-9597. - Resolution: Invalid > FileSystem open() API is not clear if FileNotFoundException is

[jira] [Created] (HADOOP-9597) FileSystem open() API is not clear if FileNotFoundException is throw when the path does not exist

Jerry He created HADOOP-9597: Summary: FileSystem open() API is not clear if FileNotFoundException is throw when the path does not exist Key: HADOOP-9597 URL: https://issues.apache.org/jira/browse/HADOOP-9597

Re: Non existent config file to 'fs -conf'

The "quiet" behavior sorta goes all the way back to the very first import of Nutch into Apache Incubator: http://svn.apache.org/viewvc?view=revision&revision=155829 and seems to deal with being relaxed about not finding added resources other than required defaults. The behavior has almost been the

Re: [DISCUSS] Ensuring Consistent Behavior for Alternative Hadoop FileSystems + Workshop

Hi Stephen Watt, I am a fresh developer trying to add a NFS-like FileSystem support for Hadoop, and also have some confusion about the FileSystem Semantics. Since I live in East Asia, I'd like to attend via Google Hangout if possible. Thanks. +1 Kun Ling yours, Kun Ling On Fr

Re: Bugfix release 2.0.4.1

>From Bigtop perspective, Hadoop  2.0.4.1 is unblocked with regards to a Sqoop >2 blocker, and the voting can be started. Anatoli -- Forwarded message -- From: Konstantin Boudnik Date: Mon, May 20, 2013 at 9:03 PM Subject: Re: Bugfix release 2.0.4.1 To: common-dev@hadoop.apache.

[jira] [Reopened] (HADOOP-8469) Make NetworkTopology class pluggable

[ https://issues.apache.org/jira/browse/HADOOP-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reopened HADOOP-8469: Backport this patch to branch-2 > Make NetworkTopology class pluggable >

Re: [DISCUSS] - Committing client code to 3rd Party FileSystems within Hadoop Common

You might try looking at what KosmoFS (KFS) did. They have some code in org/apache/hadoop/fs which calls their own Java shim. This way, the shim code in hadoop-common gets updated whenever FileSystem changes, but there is no requirement to install KFS before building Hadoop. You might also try a

[DISCUSS] Ensuring Consistent Behavior for Alternative Hadoop FileSystems + Workshop

Hi Folks Hadoop's pluggable filesystem architecture supports the ability to enable an alternate filesystem for use with Hadoop by writing a plugin for it. We now have several alternate filesystems that have Hadoop FileSystem plugins and because this isn't a very well understood topic, I've been

[jira] [Created] (HADOOP-9596) Add additional attributes to JMX beans

Trevor Lorimer created HADOOP-9596: -- Summary: Add additional attributes to JMX beans Key: HADOOP-9596 URL: https://issues.apache.org/jira/browse/HADOOP-9596 Project: Hadoop Common Issue Type

[jira] [Resolved] (HADOOP-9546) "setsid exited with exit code" message on each hadoop command

[ https://issues.apache.org/jira/browse/HADOOP-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved HADOOP-9546. Resolution: Duplicate Fixed by HADOOP-9593. > "setsid exited with exit code" mess

[jira] [Created] (HADOOP-9595) Error when error message should be printed to stderr

Alexander Veit created HADOOP-9595: -- Summary: Error when error message should be printed to stderr Key: HADOOP-9595 URL: https://issues.apache.org/jira/browse/HADOOP-9595 Project: Hadoop Common

Re: [DISCUSS] - Committing client code to 3rd Party FileSystems within Hadoop Common

Thanks for responding Harsh. I agree. Hadoop Common does do a good job of maintaining a stable and public FS and FS Context API. The pro for maintaining client libraries outside of Hadoop Common is that the release owner of the library has much more autonomy and agility in maintaining the libr

[jira] [Resolved] (HADOOP-8562) Enhancements to support Hadoop on Windows Server and Windows Azure environments

[ https://issues.apache.org/jira/browse/HADOOP-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HADOOP-8562. - Resolution: Fixed Fix Version/s: (was: 3.0.0) 2.0.5-beta I

[jira] [Reopened] (HADOOP-8562) Enhancements to support Hadoop on Windows Server and Windows Azure environments

[ https://issues.apache.org/jira/browse/HADOOP-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas reopened HADOOP-8562: - Reopening the issue for merging. > Enhancements to support Hadoop on Window

[jira] [Created] (HADOOP-9594) Update apache commons math dependency

Timothy St. Clair created HADOOP-9594: - Summary: Update apache commons math dependency Key: HADOOP-9594 URL: https://issues.apache.org/jira/browse/HADOOP-9594 Project: Hadoop Common Issue

Non existent config file to 'fs -conf'

Hi, I'm working on HADOOP-9582 and I have a question about the current implementation in hadoop-common. Here is a brief background about the bug : Basically if I give a non-exitent file to "hadoop fs –conf NONEXISTENT_FILE", the current implem

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

See Changes: [vinodkv] YARN-563. Add the concept of an application-type for each application. Contributed by Mayank Bansal. MAPREDUCE-5246. Specify application-type at the time of job submission after YARN-563. Contributed by Mayan

Re: [DISCUSS] - Committing client code to 3rd Party FileSystems within Hadoop Common

I think we do a fairly good work maintaining a stable and public FileSystem and FileContext API for third-party plugins to exist outside of Apache Hadoop but still be able to work well across versions. The question of test pops up though, specifically that of testing against trunk to catch regress

[jira] [Resolved] (HADOOP-7803) The first put to a non-existing current directory doesn't work correctly

[ https://issues.apache.org/jira/browse/HADOOP-7803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee resolved HADOOP-7803. Resolution: Duplicate > The first put to a non-existing current directory doesn't work correct

[DISCUSS] - Committing client code to 3rd Party FileSystems within Hadoop Common

(Resending - I think the first time I sent this out it got lost within all the ByLaws voting) Hi Folks My name is Steve Watt and I am presently working on enabling glusterfs to be used as a Hadoop FileSystem. Most of the work thus far has involved developing a Hadoop FileSystem plugin for glus

[jira] [Created] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set

Steve Loughran created HADOOP-9593: -- Summary: stack trace printed at ERROR for all yarn clients without hadoop.home set Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project

Re: [VOTE] Plan to create release candidate for 0.23.8

+1 (non-binding) On 05/17/2013 09:10 PM, Thomas Graves wrote: Hello all, We've had a few critical issues come up in 0.23.7 that I think warrants a 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of other issues that I want finished up and get in before we spin it. Those incl

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

See Changes: [sseth] Fixed incorrect jira in CHANGES.txt (YARN-716 to YARN-715) [sseth] YARN-716. Fixed unit test failures - TestDistributedShell and TestUnmanagedAMLauncher. Contributed by Vinod Kumar Vavilapalli. [vinodkv] MAPRE