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 81FE59BF0 for ; Tue, 11 Sep 2012 04:02:12 +0000 (UTC) Received: (qmail 58296 invoked by uid 500); 11 Sep 2012 04:02:07 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 58202 invoked by uid 500); 11 Sep 2012 04:02:07 -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 58177 invoked by uid 99); 11 Sep 2012 04:02:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2012 04:02:07 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mehmetsino@gmail.com designates 209.85.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2012 04:01:58 +0000 Received: by iecs9 with SMTP id s9so162670iec.35 for ; Mon, 10 Sep 2012 21:01:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=ShZiD5UpKwS+6/63+DTcuDUr8hAEemKoZd0P3rGhgf4=; b=eQ4MgI37oI9Mqe6CpUGeuL2AifgdQblNjtifqEa8jpaMFBggHVl9fuB0qCNtxYxhKj HPKQXQKgrpLHZe9xwZ2tmVqEin20WmRkPjmEIjmbDOiehlrfhy/dY/idubX1jjCsuqoz go7YFugcInLVfbIBMZhUsOBNn3HhNhiwM9OC224VvMkS3z3Yq2tlsNshupbP29BbvKKU Sws0CJctezsC/Fbyg+hAVgk2xEb3MntqSlQegIlEF5OSRDXqvTURx2NymTcXsHL+XHz+ XSyskvoCDIAr4P/4jzVdQt91tLs9D+F8p1Ne99I9O2WCOQ05yJ/ybelKvygi6WEUu9g2 xQ8A== Received: by 10.50.46.133 with SMTP id v5mr13897314igm.63.1347336097157; Mon, 10 Sep 2012 21:01:37 -0700 (PDT) Received: from [192.168.1.105] (adsl-69-110-145-10.dsl.pltn13.pacbell.net. [69.110.145.10]) by mx.google.com with ESMTPS id a10sm736160igd.1.2012.09.10.21.01.36 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 10 Sep 2012 21:01:36 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1278) Subject: Re: how to make different mappers execute different processing on same data ? From: Mehmet Tepedelenlioglu In-Reply-To: Date: Mon, 10 Sep 2012 21:01:34 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: user@hadoop.apache.org X-Mailer: Apple Mail (2.1278) If you have n processes to evaluate, make a reducer that calls the = process i when it receives key i, 1<=3Di<=3Dn. Either replicate the data = for the n reducers, or cache it for it to be read on the reducer side. = The reducers will output the process id i and the performance.=20 On Sep 10, 2012, at 8:25 PM, Jason Yang wrote: > Hi, all >=20 > I've got a question about how to make different mappers execute = different processing on a same data?=20 >=20 > Here is my scenario: > I got to process a data, however, there multiple choices to process = this data and I have no idea which one is better, so I was thinking that = maybe I could execute multiple mappers, in which different processing = solution is applied, and eventually the best one is chosen according to = some evaluation functions. >=20 > But I'm not sure whether this could be done in MapReduce. >=20 > Any help would be appreciated. >=20 > --=20 > YANG, Lin >=20