You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2009/05/11 20:29:45 UTC
[jira] Created: (HADOOP-5806) setProgress not called for new
RecordReaders
setProgress not called for new RecordReaders
--------------------------------------------
Key: HADOOP-5806
URL: https://issues.apache.org/jira/browse/HADOOP-5806
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Affects Versions: 0.20.0
Reporter: Chris Douglas
Priority: Blocker
NewTrackingRecordReader does not call setProgress in nextKeyValue, as the old API did
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-5806) setProgress not called for new
RecordReaders
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719682#action_12719682 ]
Owen O'Malley commented on HADOOP-5806:
---------------------------------------
+1, but it should have a test case...
> setProgress not called for new RecordReaders
> --------------------------------------------
>
> Key: HADOOP-5806
> URL: https://issues.apache.org/jira/browse/HADOOP-5806
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Chris Douglas
> Priority: Blocker
> Attachments: 5806-0.patch
>
>
> NewTrackingRecordReader does not call setProgress in nextKeyValue, as the old API did
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-5806) setProgress not called for new
RecordReaders
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708521#action_12708521 ]
Hadoop QA commented on HADOOP-5806:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12407800/5806-0.patch
against trunk revision 773836.
+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 passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/327/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/327/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/327/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/327/console
This message is automatically generated.
> setProgress not called for new RecordReaders
> --------------------------------------------
>
> Key: HADOOP-5806
> URL: https://issues.apache.org/jira/browse/HADOOP-5806
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Chris Douglas
> Priority: Blocker
> Attachments: 5806-0.patch
>
>
> NewTrackingRecordReader does not call setProgress in nextKeyValue, as the old API did
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5806) setProgress not called for new
RecordReaders
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated HADOOP-5806:
----------------------------------
Status: Patch Available (was: Open)
> setProgress not called for new RecordReaders
> --------------------------------------------
>
> Key: HADOOP-5806
> URL: https://issues.apache.org/jira/browse/HADOOP-5806
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Chris Douglas
> Priority: Blocker
> Attachments: 5806-0.patch
>
>
> NewTrackingRecordReader does not call setProgress in nextKeyValue, as the old API did
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5806) setProgress not called for new
RecordReaders
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated HADOOP-5806:
----------------------------------
Attachment: 5806-0.patch
> setProgress not called for new RecordReaders
> --------------------------------------------
>
> Key: HADOOP-5806
> URL: https://issues.apache.org/jira/browse/HADOOP-5806
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Chris Douglas
> Priority: Blocker
> Attachments: 5806-0.patch
>
>
> NewTrackingRecordReader does not call setProgress in nextKeyValue, as the old API did
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.