[
https://issues.apache.org/jira/browse/HADOOP-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613411#action_12613411
]
Doug Cutting commented on HADOOP-3715:
--------------------------------------
If we do this, it must be back-compatible. In the first release after the
change it should still accept the old names but print warnings. The suggested
way to do this is to add static accessor methods for each such parameter and
replace all accesses to the parameters with calls to the accessor methods.
Then back-compatibility can be handled centrally in the accessor methods.
Perhaps all of the accessor methods can even share a back-compatiblity
mechanism.
> Change all references of dfs to hdfs in configs
> -----------------------------------------------
>
> Key: HADOOP-3715
> URL: https://issues.apache.org/jira/browse/HADOOP-3715
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Lohit Vijayarenu
>
> After code restructuring dfs has been changed to hdfs, but I see config
> variables with dfs.<something> eg dfs.http.address. Should we change
> everything to hdfs?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
