Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 24 Mar 2011 18:17:05 +0000 (UTC)
From: "Matt Foley (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1426146929.8972.1300990625729.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1723498609.5040.1300840326140.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7207) fs member of FSShell is not really
 needed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010813#comment-13010813 ] 

Matt Foley commented on HADOOP-7207:
------------------------------------

Be careful with this one as we move to Federation, because the "-fs" command line option is currently the only way to direct the FSClient at a file system other than the default one, if any.  So if you might want your client to target one of several name services (federated namenodes), you have to use the -fs option or provide an alternative.

> fs member of FSShell is not really needed
> -----------------------------------------
>
>                 Key: HADOOP-7207
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7207
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Boris Shkolnik
>            Assignee: Boris Shkolnik
>
> FileSystem object should be created on demand when needed in FSShell, instead of always creating one that connects to the default FileSystem.
> It will also solve a problem of connecting to non-existant/non-functional default, when it is not really needed for this run.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira