[
https://issues.apache.org/jira/browse/HDFS-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748214#action_12748214
]
Owen O'Malley commented on HDFS-531:
------------------------------------
I agree with all of Tom's comments.
1. all topology stuff belongs in net.topology.
2. leave hadoop.tmp.dir alone
3. distributed cache should be mapred
4. I think we should pass on the dfs to hdfs. It would be nice, but I don't
think it is worth it.
I think dfs.max.replication.streams and dfs.heartbeat.recheck.interval should
have a more specific context? dfs.namenode.*?
> 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.
