Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Here's a jira to track deprecating 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.
3. Stabilize FileContext
Attachments
Issue Links
- is blocked by
-
HADOOP-9631 ViewFs should use underlying FileSystem's server side defaults
- Resolved
-
HADOOP-6356 Add a Cache for AbstractFileSystem in the new FileContext/AbstractFileSystem framework.
- Open
-
HADOOP-6361 Specific Exceptions thrown by FileContext and AbstractFileSystem
- Resolved
-
HDFS-876 Port tests over to FileContext/AFS
- Open
-
HADOOP-6424 Port FsShell to FileContext
- Open
-
HADOOP-6447 Port Trash to FileContext
- Open
-
HADOOP-6448 Port DistCp to FileContext.
- Open
-
HADOOP-6449 Port HarFileSystem to AbstractFileSystem
- Open
-
HDFS-943 Port DFSAdmin to FileContext
- Open
- relates to
-
HADOOP-6690 FilterFileSystem doesn't overwrite setTimes
- Closed