You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2009/03/26 11:52:08 UTC
[jira] Updated: (HADOOP-4365) Configuration.getProps() should be
made protected for ease of overriding
[ https://issues.apache.org/jira/browse/HADOOP-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated HADOOP-4365:
----------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
+1
I committed this. Thanks, Steve
> Configuration.getProps() should be made protected for ease of overriding
> ------------------------------------------------------------------------
>
> Key: HADOOP-4365
> URL: https://issues.apache.org/jira/browse/HADOOP-4365
> Project: Hadoop Core
> Issue Type: Improvement
> Components: conf
> Affects Versions: 0.21.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 0.21.0
>
> Attachments: hadoop-4365.patch, hadoop-4365.patch
>
>
> HADOOP-4293 does make Configuration cleaner and easier to work with, but it does contain assumptions about how configurations are represented (in a private Properties instance) that subclasses may wish to diverge from.
> By making getProps() protected, people who subclass JobConf or Configuration can do their own binding from configuration data to Properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.