FAQ
Configuration properties which are neither null nor final by default but are set to null and final later, are not getting set to null but marked as final.
----------------------------------------------------------------------------------------------------------------------------------------------------------

Key: HADOOP-6456
URL: https://issues.apache.org/jira/browse/HADOOP-6456
Project: Hadoop Common
Issue Type: Bug
Reporter: V.V.Chaitanya Krishna


While loading resources and programatically setting configuration properties, if a key has a non-null default value and is then set to null (either in *-site.xml or through conf.set() ), its default value is not being overridden to null. Also, if it is set to null and final in any of the resources (the default value being non-null and not final), the value is not changed to null but is marked as final. This would mean setting part of a property's content (i.e., value) from one resource and some other part of it (i.e., marking as final) from another resource which is inconsistent.

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

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedDec 18, '09 at 8:25a
activeDec 18, '09 at 8:25a
posts1
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

V.V.Chaitanya Krishna (JIRA): 1 post

People

Translate

site design / logo © 2022 Grokbase