[
https://issues.apache.org/jira/browse/HADOOP-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736672#comment-14736672
]
Hadoop QA commented on HADOOP-12374:
------------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 20m 10s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | tests included | 0m 0s | The patch doesn't appear
to include any new or modified tests. Please justify why no new tests are
needed for this patch. Also please list what manual steps were performed to
verify this patch. |
| {color:green}+1{color} | javac | 7m 54s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 59s | There were no new javadoc
warning messages. |
| {color:green}+1{color} | release audit | 0m 23s | The applied patch does
not increase the total number of release audit warnings. |
| {color:green}+1{color} | site | 3m 2s | Site still builds. |
| {color:green}+1{color} | checkstyle | 1m 8s | 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 25s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 34s | 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 | 22m 50s | Tests passed in
hadoop-common. |
| | | 69m 21s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12754875/HADOOP-12374.004.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle site |
| git revision | trunk / 0113e45 |
| hadoop-common test log |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7621/artifact/patchprocess/testrun_hadoop-common.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7621/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf903.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/7621/console |
This message was automatically generated.
> Description of hdfs expunge command is confusing
> ------------------------------------------------
>
> Key: HADOOP-12374
> URL: https://issues.apache.org/jira/browse/HADOOP-12374
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation, trash
> Affects Versions: 2.7.0, 2.7.1
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Trivial
> Labels: docuentation, newbie, suggestions, trash
> Attachments: HADOOP-12374.001.patch, HADOOP-12374.002.patch,
> HADOOP-12374.003.patch, HADOOP-12374.004.patch
>
>
> Usage: hadoop fs -expunge
> Empty the Trash. Refer to the HDFS Architecture Guide for more information on
> the Trash feature.
> this description is confusing. It gives user the impression that this command
> will empty trash, but actually it only removes old checkpoints. If user sets
> a pretty long value for fs.trash.interval, this command will not remove
> anything until checkpoints exist longer than this value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
