[ https://issues.apache.org/jira/browse/H
ADOOP-53?page=com.atlassian.jira.plugin.system.issuetabpanel
s:comment-tabpanel#action_12536140 ]
Hadoop QA commented on HADOOP-53:
---------------------------------
-1 overall. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secu
re/attachment/12367954/mapredDFSLog_v1.patch
against trunk revision r586264.
 author +1. The patch does not contain any author
tags.
javadoc -1. The javadoc tool appears to have generated
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 failed contrib unit tests.
Test results: http://lucene.zones.apache.org:8080/h
udson/job/Hadoop-Patch/970/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/j
ob/Hadoop-Patch/970/artifact/trunk/build/test/findbugs/newPa
tchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/
970/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudso
n/job/Hadoop-Patch/970/console
This message is automatically generated.
> MapReduce log files should be storable in dfs.
> ----------------------------------------------
>
> Key: HADOOP-53
> URL: https
://issues.apache.org/jira/browse/HADOOP-53
> Project: Hadoop
> Issue Type: New Feature
> Components: mapred
> Affects Versions: 0.16.0
> Reporter: Doug Cutting
> Assignee: Enis Soztutar
> Fix For: 0.16.0
>
> Attachments: mapredDFSLog_v1.patch
>
>
> It should be possible to cause a job's log output to be
stored in dfs. The jobtracker's log output and (optionally)
all tasktracker log output related to a job should be
storable in a job-specified dfs directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
