Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <15011437.1196224963063.JavaMail.jira@brutus>
Date: Tue, 27 Nov 2007 20:42:43 -0800 (PST)
From: "Devaraj Das (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-2244) MapWritable.readFields needs to clear
 internal hash else instance accumulates entries forever
In-Reply-To: <23311346.1195628743149.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devaraj Das updated HADOOP-2244:
--------------------------------

    Status: Patch Available  (was: Open)

Patch looks good. Submitting it to hudson.

> MapWritable.readFields needs to clear internal hash else instance accumulates entries forever
> ---------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2244
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2244
>             Project: Hadoop
>          Issue Type: Bug
>          Components: io
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.16.0
>
>         Attachments: 2244-v2.patch, hadoop-2244.patch
>
>
> A common framework pattern is to get an instance of a Writable, usually by reflection, and then just keep calling readFields to make new 'instances' of the particular Writable.
> For example, the spill-to-disk that is run at the end of a map task gets instances of map output keys and values and then loops over the (sorted) map output calling readFields to make instances to write out to the filesystem (See around line #470 in the spill method).
> If the particular Writable is an instance of MapWritable, currently we get funny results.  It has an internal hash map that is created on instantiation.  Each time the readFields method is called, the newly deserialized entries are added to the internal map.  The map needs to be reset when readFields is called so it doesn't just keep growing ad infinitum.

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