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 "Eli Collins (JIRA)" <ji...@apache.org> on 2009/12/16 23:06:18 UTC

[jira] Moved: (HADOOP-6446) Removing FileSystem

     [ https://issues.apache.org/jira/browse/HADOOP-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eli Collins moved HDFS-765 to HADOOP-6446:
------------------------------------------

        Key: HADOOP-6446  (was: HDFS-765)
    Project: Hadoop Common  (was: Hadoop HDFS)

> Removing FileSystem
> -------------------
>
>                 Key: HADOOP-6446
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6446
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: Eli Collins
>
> Here's a jira to track removing FileSystem. There are two high-level tasks:
> 1. Moving clients in common and mapreduce onto FileContext. I think this is currently blocked on HADOOP-6356 and HADOOP-6361. Anything else preventing them from being moved over? Any clients we could move over today?
> 2. Moving file system implementations onto AbstractFileSystem. Currently Hdfs and FilterFS (and local and checksum) extend AFS. RawLocalFileSystem uses the delegator. S3, ftp and others need to be moved over. Don't think there's anything blocking this stuff.
> In the mean time should we mark FileSystem as deprecated? Is 23 a reasonable time frame for moving everyone off FileSystem? Seems like we want to remove FileSystem before 1.0.

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