[
https://issues.apache.org/jira/browse/HADOOP-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750121#action_12750121
]
Doug Cutting commented on HADOOP-6223:
--------------------------------------
> one could deprecate parts of FileSystem and them delete or make-package
> private its methods.
> It is simpler to simply create a new class called AbstractFileSystem
I don't see how this is simpler. It breaks existing users and implementations
just to have a different name. If we want to encourage folks to use the
FileContext API in place of the FileSystem API directly then we can deprecate
and subsequently remove utility methods in FileSystem that make it easier to
use, so that it becomes mostly a set of abstract methods. Renaming it seems
gratuitously incompatible.
> 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
>
> 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.
