[
https://issues.apache.org/jira/browse/HADOOP-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1347:
----------------------------------
Status: Open (was: Patch Available)
-1
I think this is a really bad plan. I would much prefer a programatic way of
clearing a value. In particular, there are values that have semantics for the
empty string that are different from being unset. I also think it would be very
counter-intuitive.
> 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.
