[
https://issues.apache.org/jira/browse/HADOOP-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541524
]
Hadoop QA commented on HADOOP-1917:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12369271/HADOOP-1917_7_20071110.patch
against trunk revision r593708.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1087/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1087/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1087/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1087/console
This message is automatically generated.
> Need configuration guides for Hadoop
> ------------------------------------
>
> Key: HADOOP-1917
> URL: https://issues.apache.org/jira/browse/HADOOP-1917
> Project: Hadoop
> Issue Type: Improvement
> Components: conf
> Affects Versions: 0.14.1
> Reporter: Sameer Paranjpye
> Assignee: Arun C Murthy
> Priority: Critical
> Fix For: 0.15.1
>
> Attachments: HADOOP-1917_1_20071025.patch,
> HADOOP-1917_2_20071031.patch, HADOOP-1917_3_20071031.patch,
> HADOOP-1917_4_20071105.patch, HADOOP-1917_5_20071106.patch,
> HADOOP-1917_6_20071106.patch, HADOOP-1917_7_20071110.patch
>
>
> We've recently had a spate of questions on the users list regarding features
> such as rack-awareness, the trash can etc. which are not clearly documented
> from a user/admins perspective. There is some Javadoc present but most of the
> "documentation" exists either in JIRA or in the default config files
> themselves.
> We should generate top down configuration and use guides for map/reduce and
> HDFS. These should probably be in forest and accessible from the project
> website (Javadoc isn't always approachable to our non-programmer audience).
> Committers should look for user documentation before accepting patches.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
