[
https://issues.apache.org/jira/browse/HADOOP-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545032
]
Eelco Lempsink commented on HADOOP-1347:
----------------------------------------
Arun,
Unsetting values is useful when loading several configurations. After the
default configuration is loaded, a user configuration should be able to unset
values. I can't remember exactly, but I ran in to this bug when using Nutch and
trying to disable all filters for a certain part of the process.
Other than that, I don't think it's semantically correct to ignore explicit
empty configuration values.
> 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.
