[
https://issues.apache.org/jira/browse/HADOOP-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274492#comment-13274492
]
Hadoop QA commented on HADOOP-8362:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12526719/HADOOP-8362.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 javac. The patch appears to cause the build to fail.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/993//console
This message is automatically generated.
> Improve exception message when Configuration.set() is called with a null key
> or value
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-8362
> URL: https://issues.apache.org/jira/browse/HADOOP-8362
> Project: Hadoop Common
> Issue Type: Improvement
> Components: conf
> Affects Versions: 2.0.0
> Reporter: Todd Lipcon
> Priority: Trivial
> Labels: newbie
> Attachments: HADOOP-8362.patch
>
>
> Currently, calling Configuration.set(...) with a null value results in a
> NullPointerException within Properties.setProperty. We should check for null
> key/value and throw a better exception.
--
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
