[
https://issues.apache.org/jira/browse/HADOOP-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711669#action_12711669
]
Steve Loughran commented on HADOOP-5200:
----------------------------------------
the fix to NameNode for this is
public static InetSocketAddress getAddress(Configuration conf) {
URI fsURI = FileSystem.getDefaultUri(conf);
if (fsURI == null) {
throw new IllegalArgumentException(
"No default filesystem URI in the configuration");
}
String auth = fsURI.getAuthority();
if (auth == null) {
throw new IllegalArgumentException(
"No authority for the Filesystem URI " + fsURI);
}
return getAddress(auth);
}
I've incorporated it into HADOOP-3628, but it is standalone and the three unit
tests it needs wouldn't even need a namenode to be created.
> NPE when the datanode comes up but the filesystem is set to file://
> -------------------------------------------------------------------
>
> Key: HADOOP-5200
> URL: https://issues.apache.org/jira/browse/HADOOP-5200
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.21.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> If you bring up a namenode and the conf file points to file:/// as the URI,
> then the authority is null, breaking code that follows
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
