Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DF75CDF8D for ; Tue, 9 Oct 2012 07:46:06 +0000 (UTC) Received: (qmail 48401 invoked by uid 500); 9 Oct 2012 07:46:06 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 48273 invoked by uid 500); 9 Oct 2012 07:46:05 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 47815 invoked by uid 99); 9 Oct 2012 07:46:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 07:46:04 +0000 Date: Tue, 9 Oct 2012 07:46:04 +0000 (UTC) From: "Daniel Dai (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1410339480.13394.1349768764634.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Daniel Dai created HADOOP-8904: ---------------------------------- Summary: 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 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