Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 87406 invoked from network); 23 Dec 2009 01:13:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Dec 2009 01:13:57 -0000 Received: (qmail 75445 invoked by uid 500); 23 Dec 2009 01:13:57 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 75372 invoked by uid 500); 23 Dec 2009 01:13:57 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 75362 invoked by uid 99); 23 Dec 2009 01:13:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2009 01:13:57 +0000 X-ASF-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2009 01:13:50 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 93436234C1EF for ; Tue, 22 Dec 2009 17:13:30 -0800 (PST) Message-ID: <1626510403.1261530810602.JavaMail.jira@brutus> Date: Wed, 23 Dec 2009 01:13:30 +0000 (UTC) From: "Chris Douglas (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Updated: (MAPREDUCE-1329) Make MapTask.MapOutputBuffer logic more understandable In-Reply-To: <1101650366.1261530810544.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas updated MAPREDUCE-1329: ------------------------------------- Description: As noted [here|https://issues.apache.org/jira/browse/MAPREDUCE-64?focusedCommentId=12790569&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12790569], the collection logic could be clarified by explicitly separating states rather than inferring status by examining low-level markers. Similarly, abstractions for metadata, etc. should replace the offset arithmetic currently in use. (was: As noted [here|https://issues.apache.org/jira/browse/MAPREDUCE-64?focusedCommentId=12790569&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12790569], the collection logic could be clarified by explicitly separating states rather than inferring status by examining low-level markers. Similarly, abstractions for metadata, etc. should replace the offset arithmetic that ) > Make MapTask.MapOutputBuffer logic more understandable > ------------------------------------------------------ > > Key: MAPREDUCE-1329 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1329 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: task > Reporter: Chris Douglas > Assignee: Chris Douglas > > As noted [here|https://issues.apache.org/jira/browse/MAPREDUCE-64?focusedCommentId=12790569&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12790569], the collection logic could be clarified by explicitly separating states rather than inferring status by examining low-level markers. Similarly, abstractions for metadata, etc. should replace the offset arithmetic currently in use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.