hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Zeyliger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5687) Hadoop NameNode throws NPE if fs.default.name is the default value
Date Wed, 06 May 2009 17:09:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706521#action_12706521

Philip Zeyliger commented on HADOOP-5687:

The only failure I found was:

[0]doorstop:Downloads(73605)$grep "\[junit\] Test.*FAILED" consoleText
     [exec]     [junit] Test org.apache.hadoop.mapred.TestCapacitySchedulerConf FAILED

This doesn't look related, and, indeed, running "ant -Dtestcase=TestCapacitySchedulerConf
test" on a clean version of trunk triggers this error too.

Are we ok with this going in without unit tests, or should I write something that tests that
the right exception is thrown?

> Hadoop NameNode throws NPE if fs.default.name is the default value
> ------------------------------------------------------------------
>                 Key: HADOOP-5687
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5687
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>            Priority: Minor
>         Attachments: HADOOP-5687-v3.patch, HADOOP-5687-v4.patch, HADOOP-5687-v5.patch,
HADOOP-5687.patch, HADOOP-5687.patch
> Throwing NPE is confusing; instead, an exception with a useful string description could
be thrown instead.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message