Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1244852987.1234715219854.JavaMail.jira@brutus>
Date: Sun, 15 Feb 2009 08:26:59 -0800 (PST)
From: "Jothi Padmanabhan (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4927) Part files on the output filesystem
 are created irrespective of whether the corresponding task has anything to
 write there
In-Reply-To: <1373445464.1229925644193.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-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673678#action_12673678 ] 

Jothi Padmanabhan commented on HADOOP-4927:
-------------------------------------------

The test that timed out org.apache.hadoop.mapred.TestTaskLimits.testTaskLimits passed on my local machine and this test is unrelated to the patch.

> Part files on the output filesystem are created irrespective of whether the corresponding task has anything to write there
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4927
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4927
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: mapred
>            Reporter: Devaraj Das
>            Assignee: Jothi Padmanabhan
>             Fix For: 0.21.0
>
>         Attachments: hadoop-4927-v1.patch, hadoop-4927-v2.patch, hadoop-4927-v3.patch, hadoop-4927-v4.patch, hadoop-4927-v5.patch, hadoop-4927.patch
>
>
> When OutputFormat.getRecordWriter is invoked, a part file is created on the output filesystem. But the created RecordWriter is not used until the OutputCollector.collect call is made by the task (user's code). This results in empty part files even if the OutputCollector.collect is never invoked by the corresponding tasks.

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