Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 18 Oct 2012 04:22:05 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <655964221.62099.1350534125389.JavaMail.jiratomcat@arcas>
In-Reply-To: <1410339480.13394.1349768764634.JavaMail.jiratomcat@arcas>
Subject: [jira] [Assigned] (HADOOP-8904)  Hadoop does not close output file
 / does not call Mapper.cleanup if exception in map
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas reassigned HADOOP-8904:
---------------------------------------

    Assignee: Daniel Dai
    
>  Hadoop does not close output file / does not call Mapper.cleanup if exception in map
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8904
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8904
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 1-win
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>         Attachments: HADOOP-8904-1.patch
>
>
> Find this in Pig unit test TestStore under Windows. There are dangling files because map does not close the file when exception happens in map(). In Windows, Hadoop will not remove a file if it is not closed. This happens in reduce() as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira