Return-Path: 
 <common-user-return-20434-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-common-user-archive@www.apache.org
Received: (qmail 39858 invoked from network); 14 Feb 2010 00:03:10 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 14 Feb 2010 00:03:10 -0000
Received: (qmail 78414 invoked by uid 500); 14 Feb 2010 00:03:03 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 78324 invoked by uid 500); 14 Feb 2010 00:03:03 -0000
Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-user@hadoop.apache.org>
List-Id: <common-user.hadoop.apache.org>
Reply-To: common-user@hadoop.apache.org
Delivered-To: mailing list common-user@hadoop.apache.org
Received: (qmail 78305 invoked by uid 99); 14 Feb 2010 00:03:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Feb 2010 00:03:03 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates
 209.85.222.174 as permitted sender)
Received: from [209.85.222.174] (HELO mail-pz0-f174.google.com)
 (209.85.222.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Feb 2010 00:02:54 +0000
Received: by pzk4 with SMTP id 4so3978801pzk.5
        for <multiple recipients>; Sat, 13 Feb 2010 16:02:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:cc:content-type;
        bh=9JvVi8y1UkG68ZO69+EuCxzeysz2StisWmAh9Vpxe0A=;
        b=UvjHezeuaD0JW9RSbVE3G0B2LC0tAYxJasgvnEq7vL3gFAOXIdBl+1as7V+eFfdFIZ
         gUJ4eSFFW/DJivNnjbjlEYU+2y4PQVuwcJrCD22l8wrvNYDl/35JkC+yLb8VRNJAErve
         iybhxZwLziJ/uvHaGzMew83AvtIB+Ic92gO64=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=iEMXcSCuL89Bpp6PXpsh1R+bNhzkhAh3zHhJC1ZufeeYLH1KCWLDNyiLBpSWB0gkBu
         tkUdbYHvBD/cm1a6R0s+mT9id1QymA2ocYGtqP4KLh7c9Wyhsq3muqtaBjoDoXdHFhTf
         iIMyXNU1jRETAow4pe8yS7RXHdufwEpHDu6qs=
MIME-Version: 1.0
Received: by 10.142.7.16 with SMTP id 16mr2189711wfg.117.1266105752527; Sat,
	13 Feb 2010 16:02:32 -0800 (PST)
In-Reply-To: <27575531.post@talk.nabble.com>
References: <27575531.post@talk.nabble.com>
Date: Sat, 13 Feb 2010 16:02:32 -0800
Message-ID: <17e273101002131602k19078828k435ecdb74569a61a@mail.gmail.com>
Subject: Re: Pass the TaskId from map to Reduce
From: Ted Yu <yuzhihong@gmail.com>
To: common-user@hadoop.apache.org
Cc: core-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

The number of map tasks is normally different from the number of reduce tasks.
Coding as you planned would limit the flexibility of hadoop.

On Saturday, February 13, 2010, ANKITBHATNAGAR <abhatnagar@vantage.com> wrote:
>
> Hi,
>
> I was working on a scenario where in I am generating a file in close()
> function of my Map implementation.
>
> Since Map execution are worked concurrently, this file is overwritten.
>
> I was wondering how to name this file uniquely per map execution basic and
> then read in configure() function of reduce.
>
> I could give a task id as name of the file but dont know how will I read the
> same file in configure() as the task id would have changed
>
> Ankit
> --
> View this message in context: http://old.nabble.com/Pass-the-TaskId-from-map-to-Reduce-tp27575531p27575531.html
> Sent from the Hadoop core-user mailing list archive at Nabble.com.
>
>