[
https://issues.apache.org/jira/browse/HADOOP-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753277#action_12753277
]
Jitendra Nath Pandey commented on HADOOP-6233:
----------------------------------------------
> I'm concerned about having all the key changes for all across the project
> clustered in one file, and more so that there's a separate file for just the
> fs. It seems to me this will lead to confusion about updating those values or
> adding new ones. Might it be better to include that info in the relevant file?
I think it will be better to have just one class having all the configuration
keys for entire common project, i.e. we should merge fs keys and other common
keys into one single file. In my opinion, it will be easier for the users and
developers if there is a single place to look for config keys or to add new
keys. Also, since we have common configuration files, it will be better to have
a common place to hold the config keys too, like in
src/java/org/apache/hadoop/conf/CommonConfigurationKeys.java.
> Changes in common to rename the config keys as detailed in HDFS-531.
> --------------------------------------------------------------------
>
> Key: HADOOP-6233
> URL: https://issues.apache.org/jira/browse/HADOOP-6233
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Fix For: 0.21.0
>
> Attachments: HADOOP-6233.1.patch, HADOOP-6233.2.patch,
> HADOOP-6233.3.patch
>
>
> This jira tracks the code changes required in common to rename the config
> keys. The list of changed keys is attached to HDFS-531.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
