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 C47DB9B61 for ; Tue, 11 Sep 2012 03:33:55 +0000 (UTC) Received: (qmail 95680 invoked by uid 500); 11 Sep 2012 03:33:50 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 95546 invoked by uid 500); 11 Sep 2012 03:33:50 -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 95530 invoked by uid 99); 11 Sep 2012 03:33:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2012 03:33:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lin.yang.jason@gmail.com designates 209.85.220.176 as permitted sender) Received: from [209.85.220.176] (HELO mail-vc0-f176.google.com) (209.85.220.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2012 03:33:43 +0000 Received: by vcbfl11 with SMTP id fl11so79317vcb.35 for ; Mon, 10 Sep 2012 20:33:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=t3kA+7dyhBbS/FbF25xSKFn3id3C6EgRqB3SqAir+hM=; b=K7/Jn28sB1cb316TisY+1Nh0HV0O5/+OeTAwW91+YCvW8le+yC958mlAdczyR+F4PH p+1yVbjlmkBEAl2b2MkjLEFpuG49ivN2r0FollRxVosNON/Ll1Y5C/bKvBhTOfvZ/6mN 8Vl1MqIUbEY/NSJlkUMtuS0XItoOCZ3nfi856rPecKDcE6NOLASpcLmmdAVm5rE6vZxG DlQEFlcS/2WnfZAX6jDpBGPX6CERrHc2wPCLJV6rBJw+8/Xf0xiZFQeff2ZM9pqQMMp2 NtZXev+nIgDf2xWq8lsOp+2/0Am8uusX5YzprwTr86gPflsSuQl2fK65UxbDuOcneHo3 CvSg== Received: by 10.52.26.137 with SMTP id l9mr18353902vdg.62.1347334402604; Mon, 10 Sep 2012 20:33:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.132.176 with HTTP; Mon, 10 Sep 2012 20:33:02 -0700 (PDT) From: Jason Yang Date: Tue, 11 Sep 2012 11:33:02 +0800 Message-ID: Subject: How to make different mappers execute different processing on a same data ? To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf307cfd3676000c04c964bc7c X-Virus-Checked: Checked by ClamAV on apache.org --20cf307cfd3676000c04c964bc7c Content-Type: text/plain; charset=ISO-8859-1 Hi, all I've got a question about how to make different mappers execute different processing on a same data? 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. But I'm not sure whether this could be done in MapReduce. Any help would be appreciated. -- YANG, Lin --20cf307cfd3676000c04c964bc7c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi, all

I've got a question abo= ut how to make different mappers execute different processing on a same dat= a?=A0

Here is my scenario:
I got to pr= ocess a data, however, there multiple choices to process this data and I ha= ve no idea which one is better, so I was thinking that maybe I could execut= e multiple mappers, in which different processing solution is applied, and = eventually the best one is chosen according to some evaluation functions.

But I'm not sure whether this could be done in MapReduce.

Any help would be appreciated.

--
YANG, Lin
--20cf307cfd3676000c04c964bc7c--