Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <114079731.1255119211399.JavaMail.jira@brutus>
Date: Fri, 9 Oct 2009 13:13:31 -0700 (PDT)
From: "Doug Cutting (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=12764177#action_12764177 ] 

Doug Cutting commented on HADOOP-6302:
--------------------------------------

I agree that this feels wrong.  It puts HDFS in a privileged position that could be abused, if only inadvertently.

But we might still do this.

We've already embraced the dependency order of common<hdfs<mapreduce, right?  The primary users who benefit from an abstract filesystem API are mapreduce users, who're already now dependent on HDFS.  This change only affects filesystem API users who use neither HDFS nor MapReduce.  Are there any such?

I wish we could have found a way to make MapReduce depend directly on Common.  The problem as I understood it was tests: it's nice to keep tests with the code they test, and its also nice to test MapReduce with HDFS.  I suggested that we might use a higher-level build that keeps tests with their projects but builds tests after both mapreduce and hdfs core, but that's perhaps not workable long-term, if we really want these to be able to evolve as separate projects with separate release schedules.

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