[ https://issues.apache.org/jira/browse/HADOOP-11302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219040#comment-14219040 ]
Colin Patrick McCabe commented on HADOOP-11302: ----------------------------------------------- To be honest, I don't see the value in protecting against the second case. If users want to load a configuration and modify it, they always can... if by no other way, then by making a copy with the differences they want. {{final}} Configuration keys were about making XML files work better (for some definition of "better"...) > Configuration#set method should honor final properties > ------------------------------------------------------ > > Key: HADOOP-11302 > URL: https://issues.apache.org/jira/browse/HADOOP-11302 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 2.5.1 > Reporter: Kannan Rajah > Assignee: Kannan Rajah > Attachments: final-properties.patch > > > Configuration class has several methods to add a configuration resource. The > properties of this resource can override properties of previously added > resources, unless they were marked final. According to the Javadoc for > Configuration.java, the check for final properties is done > only while loading resources. But it makes sense to do this check in the set > API as well. Otherwise, users will be able to override final properties set > by admin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)