[
https://issues.apache.org/jira/browse/HDFS-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742311#action_12742311
]
Tom White commented on HDFS-531:
--------------------------------
* It seems wrong that there are HDFS properties in Common. Rather than
dfs.networktopology.* how about net.topology.* to reflect the fact they are in
the o.a.h.net package? Also, why not keep hadoop.tmp.dir instead of renaming it
dfs.tmp.dir?
* The distributed cache is moving to MapReduce so filecache.local.cache.size,
should have a mapred prefix. See also MAPREDUCE-711.
* My preference would be that the HDFS prefix is hdfs, not dfs, to be
consistent with the protocol scheme (hdfs://) and package names (o.a.h.hdfs).
But this is a big change.
> Renaming of configuration keys
> ------------------------------
>
> Key: HDFS-531
> URL: https://issues.apache.org/jira/browse/HDFS-531
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Fix For: 0.21.0
>
> Attachments: changed_config_keys.txt
>
>
> Keys in configuration files should be standardized so that key names reflect
> the components they are used in.
> For example:
> dfs.backup.address should be renamed to dfs.namenode.backup.address
> dfs.data.dir should be renamed to dfs.datanode.data.dir
> This change will impact both hdfs and common sources.
> Following convention is proposed:
> 1. Any key related hdfs should begin with 'dfs'.
> 2. Any key related to namenode, datanode or client should begin with
> dfs.namenode, dfs.datanode or dfs.client respectively.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
