[
https://issues.apache.org/jira/browse/HADOOP-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Radia updated HADOOP-6223:
---------------------------------
Attachment: Hdfs.java
AbstractFileSystem.java
I have attached a draft for AbstractFileSystem and one impl Hdfs.
Will add a delegator class that delegates calls to old Filesystem for all the
other filesystems (local fs, s3, kfs etc).
Q. Strictly speaking AbstractFileSystem should take a slash-relative name or or
Fully-qualified-uri
that is for the *this* filesystem.
Should we restrict AbstractFileSystem to require fully-qualified pathnames? My
current impl does that to
help me catch bugs in the upper layer (FileContext) that accidently sends a
slash-path name to the wrong file system.
(The glob code btw had such a bug.)
> New improved FileSystem interface for those implementing new files systems.
> ---------------------------------------------------------------------------
>
> Key: HADOOP-6223
> URL: https://issues.apache.org/jira/browse/HADOOP-6223
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Attachments: AbstractFileSystem.java, Hdfs.java
>
>
> The FileContext API (HADOOP-4952) provides an improved interface for the
> application writer.
> This lets us simplify the FileSystem API since it will no longer need to deal
> with notions of default filesystem [ / ], wd, and config
> defaults for blocksize, replication factor etc. Further it will not need the
> many overloaded methods for create() and open() since
> the FileContext API provides that convenience.
> The FileSystem API can be simplified and can now be restricted to those
> implementing new file systems.
> This jira proposes that we create new file system API, and deprecate
> FileSystem API after a few releases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
