[
https://issues.apache.org/jira/browse/HADOOP-12065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574215#comment-14574215
]
Hadoop QA commented on HADOOP-12065:
------------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 16m 35s | Pre-patch HDFS-7285 compilation
is healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:green}+1{color} | tests included | 0m 0s | The patch appears to
include 1 new or modified test files. |
| {color:green}+1{color} | javac | 7m 32s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 44s | There were no new javadoc
warning messages. |
| {color:red}-1{color} | release audit | 0m 14s | The applied patch generated
1 release audit warnings. |
| {color:green}+1{color} | checkstyle | 1m 7s | There were no new checkstyle
issues. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | install | 1m 36s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 32s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 1m 52s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | common tests | 23m 12s | Tests passed in
hadoop-common. |
| | | 62m 29s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12737872/HADOOP-12065-HDFS-7285-v1.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | HDFS-7285 / c0929ab |
| Release Audit |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6928/artifact/patchprocess/patchReleaseAuditProblems.txt
|
| hadoop-common test log |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6928/artifact/patchprocess/testrun_hadoop-common.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6928/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf909.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6928/console |
This message was automatically generated.
> Using more meaningful keys in EC schema
> ---------------------------------------
>
> Key: HADOOP-12065
> URL: https://issues.apache.org/jira/browse/HADOOP-12065
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: io
> Reporter: Kai Zheng
> Assignee: Kai Zheng
> Attachments: HADOOP-12065-HDFS-7285-v1.patch
>
>
> Commented by [~szetszwo] in HADOOP-12029:
> bq. We should also change "k" and "m" in the following to something like
> "numDataUnits" and "numParityUnits".
> {code}
> public static final String NUM_DATA_UNITS_KEY = "k";
> public static final String NUM_PARITY_UNITS_KEY = "m";
> {code}
> This sounds good to me, as in fact in many erasure coding related papers,
> discussions, and implementations, though {{k}} and {{m}} are broadly used,
> the meanings are not consistent. For example, {{m}} can also mean
> {{numDataUnits + numParityUnits}}, all the rows in the coding matrix. The
> suggested names are more clear and explicit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
