[
https://issues.apache.org/jira/browse/HADOOP-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675558#action_12675558
]
Hadoop QA commented on HADOOP-5222:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12400340/clienttrace-1.patch
against trunk revision 746340.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3891/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3891/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3891/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3891/console
This message is automatically generated.
> Add offset in client trace
> --------------------------
>
> Key: HADOOP-5222
> URL: https://issues.apache.org/jira/browse/HADOOP-5222
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Reporter: Lei Xu
> Assignee: Lei Xu
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: clienttrace-1.patch, clienttrace.patch
>
>
> By adding offset in client trace, the client trace information can provide
> more accurately information about I/O.
> It is useful for performance analyzing.
> Since there is no random write now, the offset of writing is always zero.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
