hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-631) Changes in HDFS to rename the config keys as detailed in HDFS-531.
Date Thu, 01 Oct 2009 01:37:23 GMT

    [ https://issues.apache.org/jira/browse/HDFS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761077#action_12761077

Jakob Homan commented on HDFS-631:

OK, trunk.6 patch looks good. +1 as long as the following two items are taken care of:
  * There are still some conf values not set by String constants but rather string literals.
 Another jira should be opened to finish this conversion.
  * We should do a pass over the user-facing documentation and check that any conf names that
have been changed in this patch are also changed in the documentation.  This can also be done
in a separate jira.

Also, for the conf file versioning, we should probably keep to what we do with protocols and
versions, noting the reason for the last change in number (such as ClientProtocol version).
 If we are going to bump the number for each new configuration value, we'll need to make sure
that's enforce through code review.

> Changes in HDFS to rename the config keys as detailed in HDFS-531.
> ------------------------------------------------------------------
>                 Key: HDFS-631
>                 URL: https://issues.apache.org/jira/browse/HDFS-631
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: 0.21.0
>         Attachments: HDFS-631.1.patch, HDFS-631.21-append.1.patch, HDFS-631.21-append.2.patch,
HDFS-631.21-append.3.patch, HDFS-631.trunk.2.patch, HDFS-631.trunk.4.patch, HDFS-631.trunk.5.patch,
> This jira tracks the code changes required in HDFS 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.

View raw message