[HDFS-531] Renaming of configuration keys

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.21.0
• Assignee: Jitendra Nath Pandey
• Reporter: Jitendra Nath Pandey
• Created: 06/Aug/09 18:01
• Updated: 02/May/13 02:29
• Resolved: 10/Aug/10 18:38

Description

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.

Issue Links

• depends upon: HADOOP-6105 Provide a way to automatically handle backward compatibility of deprecated keys
• is depended upon by: HADOOP-6233 Changes in common to rename the config keys as detailed in HDFS-531.
• relates to: HDFS-631 Changes in HDFS to rename the config keys as detailed in HDFS-531.
• relates to: MAPREDUCE-849 Renaming of configuration property names in mapreduce