Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D29417268 for ; Tue, 24 Mar 2015 20:19:23 +0000 (UTC) Received: (qmail 50677 invoked by uid 500); 24 Mar 2015 20:18:44 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 50551 invoked by uid 500); 24 Mar 2015 20:18:44 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 50540 invoked by uid 99); 24 Mar 2015 20:18:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Mar 2015 20:18:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.213.169 as permitted sender) Received: from [209.85.213.169] (HELO mail-ig0-f169.google.com) (209.85.213.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Mar 2015 20:18:18 +0000 Received: by igcxg11 with SMTP id xg11so8164137igc.0 for ; Tue, 24 Mar 2015 13:18:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=g/pk6cWI002qYd7Cd4TacY9wog64S2HuHlljvl9hIyU=; b=iKcaA+hTEGtULTBaE2Fw8RvVafWhW63uWOi8gEM+UH0vk/yoNDIKX/EHBspMJp43KY WErzhZJU3KP6bPD0y0Mmjr5Gu1mCf4aaUX4nT/+H7Nz+tKDzPKiIAXrhS2dxAZ4JzfJq u2GxPT4QueslnunyNjLvdl3eRFcDhv/hbjLKn+xfQPmR3/WBuhOpz1BYPzQzx0SkcF0R k+Z6tooP0Cm65AO8r0sJqJ0uuZuKu+wMCapcjgJDV+QGtGa2eSYi14cUX6xi6i0dmilV +Kk3VsN1eki2291UcBjVa+O6K0ImwA0DEpXvN3RY2XASrShm47/L/+SiSMCfBxFzD/ek /gSA== X-Gm-Message-State: ALoCoQkyhxZ5BnXKcisYZuvN2Bv+wHnoKUuL+9DQBSDtMfr9P4IRbkulD6VIrWnVGqsEzt3yyFTN X-Received: by 10.50.122.68 with SMTP id lq4mr24677227igb.10.1427228296593; Tue, 24 Mar 2015 13:18:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.9.144 with HTTP; Tue, 24 Mar 2015 13:17:56 -0700 (PDT) In-Reply-To: <550C0818.4080805@gmail.com> References: <550C0818.4080805@gmail.com> From: Harsh J Date: Wed, 25 Mar 2015 01:47:56 +0530 Message-ID: Subject: Re: Tell which reduce task run which partition To: "" Content-Type: multipart/alternative; boundary=089e015383fca1e2dd05120e7bdd X-Virus-Checked: Checked by ClamAV on apache.org --089e015383fca1e2dd05120e7bdd Content-Type: text/plain; charset=UTF-8 Your example is the reality case. The reducer ID matches its partition integer. On Fri, Mar 20, 2015 at 5:14 PM, xeonmailinglist-gmail < xeonmailinglist@gmail.com> wrote: > Hi, > > Is there a way to tell which Reduce tasks will run which partition? E.g, I > want that reduce task 00000 will read partition 0, reduce task 00001 will > read partition 1, etc... > > Thanks, > > -- > -- > > -- Harsh J --089e015383fca1e2dd05120e7bdd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Your example is the reality case. The reducer ID matches i= ts partition integer.

On Fri, Mar 20, 2015 at 5:14 PM, xeonmailinglist-gmail <xeonma= ilinglist@gmail.com> wrote:

Hi,

Is there a way to tell which Reduce tasks will run which partition? E.g, I = want that reduce task 00000 will read partition 0, reduce task 00001 will r= ead partition 1, etc...

Thanks,

--
--

Harsh J

--089e015383fca1e2dd05120e7bdd--