[
https://issues.apache.org/jira/browse/HDFS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272676#comment-13272676
]
Hadoop QA commented on HDFS-3372:
---------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12526388/HDFS-3372.002.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+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 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2407//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2407//console
This message is automatically generated.
> offlineEditsViewer should be able to read a binary edits file with recovery
> mode
> --------------------------------------------------------------------------------
>
> Key: HDFS-3372
> URL: https://issues.apache.org/jira/browse/HDFS-3372
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Attachments: HDFS-3372.001.patch, HDFS-3372.002.patch
>
>
> It would be nice if oev (the offline edits viewer) had a switch that allowed
> us to read a binary edits file using recovery mode. oev can be very useful
> when working with corrupt or messed up edit log files, and this would make it
> even more so.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
