[
https://issues.apache.org/jira/browse/HADOOP-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281254#comment-13281254
]
Eli Collins commented on HADOOP-8422:
-------------------------------------
Should we add the new FileSystem#getDefault* methods that take a Path to Hadoop
1.x?
The problem is that the ViewFileSystem defaults throw an exception now so
programs like HBase break on viewfs enabled clients because they don't use the
new methods that take a path (because these don't exist in Hadoop 1.x) and the
versions that don't take a path don't work, eg
{noformat}
2012-05-17 14:02:14,328 ERROR
org.apache.hadoop.hbase.regionserver.HRegionServer: Failed init
org.apache.hadoop.fs.viewfs.NotInMountpointException: getDefaultBlockSize on
empty path is invalid
at
org.apache.hadoop.fs.viewfs.ViewFileSystem.getDefaultBlockSize(ViewFileSystem.java:488)
at org.apache.hadoop.hbase.regionserver.wal.HLog.<init>(HLog.java:377)
{noformat}
Since there's no notion of "default file system" for a viewfs mount table I
agree that throwing an exception for the non-path case is the right call.
> 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: 2.0.0
> Reporter: 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
