[ https://issues.apache.org/jira/browse/HADOOP-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281870#comment-13281870 ]
Eli Collins commented on HADOOP-8422: ------------------------------------- One reason I'm not super thrilled with backporting the new APIs from HADOOP-8014 to branch-1 and introducing uses of them in other projects like HBase is that it means new HBase releases won't work on all but the most recent releases of 1.x. This is a rare / unfortunate case where federation violates the FileSystem API (which assumes there's a default file system associated with a FileSystem object) so users who want to support federation have to give up working transparently on older releases. Don't see a great alternative though, and at least this gives people a transition path. Here's my proposal: # Deprecate the FileSystem#getDefault* and getServerDefault methods that don't take a Path in trunk and branch-2 since these uses aren't valid (their programs will break if the user ever switches to using viewfs) # Add the methods that take a Path to branch-1 for the Hadoop 1.1 release so people can transition Reasonable? > FileSystem#getDefaultBlockSize and Replication don't use the given path > ----------------------------------------------------------------------- > > Key: HADOOP-8422 > URL: https://issues.apache.org/jira/browse/HADOOP-8422 > Project: Hadoop Common > Issue Type: Bug > Components: fs > Affects Versions: 1.0.3 > Reporter: Eli Collins > Assignee: Eli Collins > Priority: Minor > > The javadocs for FileSystem#getDefaultBlockSize and > FileSystem#getDefaultReplication claim that "The given path will be used to > locate the actual filesystem" however they both ignore the path. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira