hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1900) Remove HDFS-specific configuration keys defined in FsConfig
Date Tue, 01 Nov 2011 01:09:41 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eli Collins updated HDFS-1900:
------------------------------

    Description: HADOOP-4952 added a couple HDFS-specific configuration values to common (the
block size and the replication factor) that conflict with the HDFS values (eg have the wrong
defaults, wrong key name), are not used by common or hdfs and should be removed. After removing
these I noticed the rest of FsConfig is only used once outside a test, and isn't tagged as
a public API, I think we can remove it entirely.  (was: HADOOP-4952 added a dfs.block.size
key to common configuration, defined in o.a.h.fs.FsConfig. This conflicts with the original
HDFS block size key of the same name, which is now deprecated in favor of dfs.blocksize. It
doesn't make sense to have two different keys for the block size (ie they can disagree). Why
doesn't HDFS just use the key defined in common?)
       Assignee: Eli Collins  (was: Abel Perez)
         Labels:   (was: newbie)
        Summary: Remove HDFS-specific configuration keys defined in FsConfig  (was: Use the
block size key defined by common )
    
> Remove HDFS-specific configuration keys defined in FsConfig
> -----------------------------------------------------------
>
>                 Key: HDFS-1900
>                 URL: https://issues.apache.org/jira/browse/HDFS-1900
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 0.21.1
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: HDFS-1900.txt
>
>
> HADOOP-4952 added a couple HDFS-specific configuration values to common (the block size
and the replication factor) that conflict with the HDFS values (eg have the wrong defaults,
wrong key name), are not used by common or hdfs and should be removed. After removing these
I noticed the rest of FsConfig is only used once outside a test, and isn't tagged as a public
API, I think we can remove it entirely.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message