[
https://issues.apache.org/jira/browse/HDFS-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053509#comment-13053509
]
Hadoop QA commented on HDFS-1900:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12483516/HDFS-1900.txt
against trunk revision 1138645.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 120 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/821//console
This message is automatically generated.
> Use the block size key defined by common
> -----------------------------------------
>
> 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: Abel Perez
> Labels: newbie
> Fix For: 0.22.0
>
> Attachments: HDFS-1900.txt
>
>
> 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?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira