[
https://issues.apache.org/jira/browse/MAPREDUCE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832975#action_12832975
]
Hadoop QA commented on MAPREDUCE-1486:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12435649/MAPREDUCE-1486.patch
against trunk revision 909241.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
+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 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/Mapreduce-Patch-h6.grid.sp2.yahoo.net/448/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/448/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/448/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/448/console
This message is automatically generated.
> Configuration data should be preserved within the same MapTask
> --------------------------------------------------------------
>
> Key: MAPREDUCE-1486
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1486
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: task
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1486.patch
>
>
> Map tasks involve a number of Contexts -- at least a TaskAttemptContext and a
> MapContext. These context objects contain a Configuration each; when one
> context is initialized, it initializes its own Configuration by deep-copying
> a previous Configuration.
> If one Context instance is used entirely prior to a second, more specific
> Context then the second Context should contain the configuration data
> initialized in the previous Context. This specifically affects the
> interaction between an InputFormat and its RecordReader instance(s).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.