Return-Path: 
 <user-return-6538-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-user-archive@www.apache.org
Delivered-To: apmail-hadoop-common-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D2A30F244
	for <apmail-hadoop-common-user-archive@www.apache.org>;
 Thu, 28 Mar 2013 08:48:39 +0000 (UTC)
Received: (qmail 9707 invoked by uid 500); 28 Mar 2013 08:48:35 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 9318 invoked by uid 500); 28 Mar 2013 08:48:34 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 9306 invoked by uid 99); 28 Mar 2013 08:48:34 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 08:48:34 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of cordioli.alberto@gmail.com
 designates 209.85.215.53 as permitted sender)
Received: from [209.85.215.53] (HELO mail-la0-f53.google.com) (209.85.215.53)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 08:48:29 +0000
Received: by mail-la0-f53.google.com with SMTP id fr10so17094290lab.40
        for <user@hadoop.apache.org>; Thu, 28 Mar 2013 01:48:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:mime-version:from:date:message-id:subject:to
         :content-type;
        bh=QFqKzuP6oZLxExck9tlKPE0GIVIy5bI1xCEnWKb4dB0=;
        b=XmchfsmkOJ6la58hwUIVk3HNhfxjbLBZyCbZ8KOpI8pExXOigiuzYkKEGIyhqqow84
         1R1yhWZYQkfYm52ysdrNzYwaQ49/C9luDEvaW57o/F823Z5rAlwjd/kR+MaqH9BA/yaj
         QwyYszkUzw95WOSS+ZUQzjPtteKkklAKoFkHObvlQyQNIlpqqbeAbHDGbp4+dprVRe5e
         koKQbnD+Ekey0RTHWMfOUFvytKCFBVNj9gtwu8YzxNnh17x7dQFXo4PVspLyM8rS1BPX
         NVUJutMnnregv71i5vso9cQjjY16ORZP81pIiFpNLvToaHy+MUy8aYzDWdesSnnETmI/
         Gjbg==
X-Received: by 10.152.112.138 with SMTP id iq10mr11877368lab.55.1364460487583;
 Thu, 28 Mar 2013 01:48:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.113.36 with HTTP; Thu, 28 Mar 2013 01:47:52 -0700 (PDT)
From: Alberto Cordioli <cordioli.alberto@gmail.com>
Date: Thu, 28 Mar 2013 09:47:52 +0100
Message-ID: 
 <CAFnReZbFc=foHA1TU=Cz7XUNUeobY6sb1HA1+dPF9-2HzpGvXg@mail.gmail.com>
Subject: Find reducer for a key
To: user@hadoop.apache.org
Content-Type: text/plain; charset=UTF-8
X-Virus-Checked: Checked by ClamAV on apache.org

Hi everyone,

how can i know the keys that are associated to a particular reducer in
the setup method?
Let's assume in the setup method to read from a file where each line
is a string that will become a key emitted from mappers.
For each of these lines I would like to know if the string will be a
key associated with the current reducer or not.

I read something about mapred.task.partition and mapred.task.id, but I
didn't understand the usage.


Thanks,
Alberto


--
Alberto Cordioli