You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Gregory Farnum (JIRA)" <ji...@apache.org> on 2009/10/08 22:13:31 UTC

[jira] Commented: (HADOOP-6302) Move FileSystem and all of the implementations to HDFS project

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

Gregory Farnum commented on HADOOP-6302:
----------------------------------------

Isn't the whole point of the FileSystem setup that MapRed, Common, et al are completely divorced from the details of HDFS? It seems like moving the interface classes into the HDFS subproject would make the other projects much more dependent on HDFS for their release cycle and make things harder on external developers trying to interface their own filesystems with the overall project.
Though my perspective on this is pretty narrow, to say the least...

> 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.