[HADOOP-6456] 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.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: V.V.Chaitanya Krishna
• Created: 18/Dec/09 08:23
• Updated: 18/Dec/09 08:30

Description

While loading resources into Configuration object, if a key has a non-null default value and is then set to null (in *-site.xml), 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.