hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6223) New improved FileSystem interface for those implementing new files systems.
Date Mon, 07 Sep 2009 19:26:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752244#action_12752244

Sanjay Radia commented on HADOOP-6223:

> I am seriously considering going with option 2.
>>Can you seriously explain why?
Mostly it is personal choice but my  reasons are:
# Since option 2 is the final state it is generally good to start with that.
# Forces one to design the AbstractFileSystem - FileContext relationship better. I had to
keep the difference between old FileSystem and the new AbstractFileSystem  clear in my head.
Comments from a few folks also confused this distinction: E.g. several folks commented  "getInitialWorkingDir()
is not needed since we have getWd'; in spite of my comment in the getInitalWD() it wasn't
clear that the new FileSystem, is not suppose to know about wd - it can have an opinion only
on the initial wd.
# Both codepaths 
** Applications to FileContext to AbstractFileSystem to AbstractFileSystemImpls and
** Applications to FileSystem to FileSystemImpls

are part of the system from the beginning. In option 2 the flip at the end introduces  the
final code path. This is better for testing.

> 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
> The FileContext API (HADOOP-4952) provides an improved interface for the application
> 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.

View raw message