[ https://issues.apache.org/jira/browse/HADOOP-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750196#action_12750196 ]
Arun C Murthy commented on HADOOP-6223: --------------------------------------- bq. Renaming it seems gratuitously incompatible. I agree that FileSystem _is_ the right name for the new class. However, I do see the danger of just re-purposing org.apache.hadoop.fs.FileSystem - it is quite dangerous for users who are skipping releases i.e. 0.20 to 0.22. Hence I propose a compromise: create a new *limited-private* org.apache.hadoop.vfs.FileSystem - we can start moving implementations of the FileSystem over right now. Thoughts? > 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.