hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-671) Documentation change for updated configuration keys.
Date Wed, 27 Apr 2011 17:42:03 GMT

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

Tom White commented on HDFS-671:
--------------------------------

> This needs to go in trunk as well right?

Correct.

> CommonConfigurationKeysPublic.java defines FS_DEFAULT_NAME_KEY as "fs.defaultFS" and
FsConfig.java defines FS_DEFAULT_NAME_KEY = "fs.default.name". Why are both needed?

This looks like an inconsistency. FsConfig is used by FileContext, and looks like its keys
need updating to be consistent with (or use) CommonConfigurationKeysPublic. This can be tackled
in another JIRA.

> Documentation change for updated configuration keys.
> ----------------------------------------------------
>
>                 Key: HDFS-671
>                 URL: https://issues.apache.org/jira/browse/HDFS-671
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Jitendra Nath Pandey
>            Assignee: Tom White
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: HDFS-671.patch
>
>
>  HDFS-531, HADOOP-6233 and HDFS-631 have resulted in changes in several config keys.
The hadoop documentation needs to be updated to reflect those changes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message