[
https://issues.apache.org/jira/browse/HADOOP-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397279#comment-13397279
]
Hadoop QA commented on HADOOP-8362:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12532650/HADOOP-8362-7.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1124//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-alpha
> Reporter: Todd Lipcon
> Assignee: madhukara phatak
> Priority: Trivial
> Labels: newbie
> Attachments: HADOOP-8362-1.patch, HADOOP-8362-2.patch,
> HADOOP-8362-3.patch, HADOOP-8362-4.patch, HADOOP-8362-5.patch,
> HADOOP-8362-6.patch, HADOOP-8362-7.patch, 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
