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 2008/07/09 03:00:33 UTC

[jira] Issue Comment Edited: (HADOOP-3721) CompositeRecordReader::next is unnecessarily complex

    [ https://issues.apache.org/jira/browse/HADOOP-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611859#action_12611859 ] 

chris.douglas edited comment on HADOOP-3721 at 7/8/08 5:58 PM:
---------------------------------------------------------------

After discussing it with Runping, it is clear that considerable state may be removed from the JoinCollector without affecting correctness or performance.

      was (Author: chris.douglas):
    After discussing it with Runping, it is clear that considerable state may be removed from the JoinCollector without affecting correctness or performance.

This patch includes HADOOP-3630.
  
> CompositeRecordReader::next is unnecessarily complex
> ----------------------------------------------------
>
>                 Key: HADOOP-3721
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3721
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Chris Douglas
>            Assignee: Chris Douglas
>             Fix For: 0.19.0
>
>         Attachments: 3721-0.patch
>
>
> Much of the join logic can be made more readable and its interfaces cleaned up. In particular, CompositeRecordReader::next would benefit from some refactoring.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.