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 "Doug Cutting (JIRA)" <ji...@apache.org> on 2008/10/07 20:00:44 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12637567#action_12637567 ]
Doug Cutting commented on HADOOP-4365:
--------------------------------------
JobConf will soon go away, with HADOOP-1230.
That said, letting folks override getProps() sounds fine. This revives the spirit of HADOOP-24.
> 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.20.0
> Reporter: Steve Loughran
>
> 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.