You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Rajagopal Natarajan (JIRA)" <ji...@apache.org> on 2007/10/29 13:21:50 UTC

[jira] Updated: (HADOOP-1347) Configuration XML bug: empty values

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

Rajagopal Natarajan updated HADOOP-1347:
----------------------------------------

    Affects Version/s:     (was: 0.12.2)
               Status: Patch Available  (was: Open)

Added a case to check if the value was previously set, to be unset, in the case where the new configuration has an empty value for the field.

> Configuration XML bug: empty values
> -----------------------------------
>
>                 Key: HADOOP-1347
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1347
>             Project: Hadoop
>          Issue Type: Bug
>          Components: conf
>            Reporter: Eelco Lempsink
>            Priority: Critical
>
> The configuration parser doesn't handle empty values well:
> if ("value".equals(field.getTagName()) && field.hasChildNodes())
> This logic makes it impossible to 'unset' a field when loading multiple configurations.

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