[
https://issues.apache.org/jira/browse/HADOOP-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754202#action_12754202
]
Doug Cutting commented on HADOOP-6223:
--------------------------------------
> You first objected to the notion of having a different class and hence the
> need for this Jira.
I questioned it, as it didn't initially seem well motivated. The changes in
semantics of same-named methods subsequently provided a compelling motivation.
That argument was not in the initial description.
> Making progress on some of these Jiras is very hard because you look at only
> bits and pieces of the puzzle [ ...]
The puzzle needs to be presented clearly to all, not in private discussions. I
have monitored all related Jira issues, and responded promptly to comments in
these. Your motivations were not clear to me until I asked some questions.
Now I can see the case for AbstractFileSystem and your option 2. I do not yet
see a case for rename2.
> The design choices I had made were reasonable and discussed extensively with
> owen, arun, chris, suresh, and others.
Can you point to these discussions? Co-location is an open-source
anti-pattern. Outsiders cannot just assume that every proposal of yours is
perfect. Proposals must succeed on merit. I scrutinize proposals that change
fundamental public APIs much more closely than other proposals. Deprecating
FileSystem is a big deal and should be done very carefully and with community
involvement.
> 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 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.
