[
https://issues.apache.org/jira/browse/HADOOP-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544976
]
Arun C Murthy commented on HADOOP-1347:
---------------------------------------
The patch looks fine, but as I noted before I'm not very sure about the merits
of allowing configurations to be 'unset'... what is the use case for this?
> 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
> Assignee: Rajagopal Natarajan
> Priority: Critical
> Attachments: unset.patch, unset_with_tests.patch,
> unset_with_tests.patch
>
>
> 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.
