hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6223) New improved FileSystem interface for those implementing new files systems.
Date Tue, 15 Sep 2009 17:45:57 GMT

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

Doug Cutting commented on HADOOP-6223:

> AFS impls all end with fs

I'd generally prefer "Fs".

When acronyms are incorporated in Java names there are two styles: all caps or capitalized.
 I prefer capitalized (e.g., FooUrl versus FooURL).  I have also seen this recommended in
several Java style guides and never the contrary, e.g.:


FTP is an independent acronym, so FtpFs is probably best.
HD and K are not independent acronyms, so "Hdfs"  and "Kfs" are probably preferred.
The rest are simpler: FilterFs, LocalFs, RawLocalFs, S3Fs, & S3NativeFs.

> 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