hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-7118) NPE in Configuration.writeXml
Date Tue, 25 Jan 2011 23:13:43 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon updated HADOOP-7118:

    Attachment: hadoop-7118.txt

Woops, patch was against yesterday's common tree, didn't apply. Take two.

> NPE in Configuration.writeXml
> -----------------------------
>                 Key: HADOOP-7118
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7118
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.22.0
>         Attachments: hadoop-7118.txt, hadoop-7118.txt
> In HADOOP-7082 I stupidly introduced a regression whereby Configuration.writeXml will
throw an NPE if it is called before any .get() call is made, since the properties member is
not initialized. This is causing a failure in TestCapacitySchedulerWithJobTracker on my box,
but doesn't appear to trigger any failures in the non-contrib tests since .get() is usually
called first.
> This JIRA is to fix the bug and add a unit test for writeXml in common (apparently it
never had a unit test)

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

View raw message