[
https://issues.apache.org/jira/browse/HADOOP-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8362:
----------------------------
Attachment: HADOOP-8362.10.patch
Had to rebase this after HADOOP-8525 made some changes.
Also fixed an extra space in midst of a javadoc sentence, and made the error
more assertive, and descriptive of the context.
Added tests were unmodified pass as before:
{code}
Running org.apache.hadoop.conf.TestConfiguration
Tests run: 50, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.544 sec
{code}
Committing this version.
> 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
> Fix For: 3.0.0
>
> 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-8.patch,
> HADOOP-8362.10.patch, HADOOP-8362.9.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
