Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <352749351.1255041511438.JavaMail.jira@brutus>
Date: Thu, 8 Oct 2009 15:38:31 -0700 (PDT)
From: "hadoopguy (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6302) Move FileSystem and all of the
 implementations to HDFS project
In-Reply-To: <2132973658.1255025851375.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

hadoopguy commented on HADOOP-6302:
-----------------------------------

I strongly agree with Gregory. Moving the FileSystem and FileContext into HDFS is not clean for other filesystem implementors. HDFS is one implementation of the FileSystem API - lets keep it separate.
Also won't the pain of the patches get reduced as we are striving hard to make the FileSystem API ready as 1.0  ?

> Move FileSystem and all of the implementations to HDFS project
> --------------------------------------------------------------
>
>                 Key: HADOOP-6302
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6302
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Owen O'Malley
>             Fix For: 0.21.0
>
>
> Currently, the FileSystem and FileContext classes are in Common and the primary implementation is in HDFS. That means that many patches span between the subprojects. I think it will reduce the pain if we move FileSystem and the dependent classes into HDFS.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.