Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 76363 invoked from network); 12 Jan 2011 18:45:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jan 2011 18:45:40 -0000 Received: (qmail 63146 invoked by uid 500); 12 Jan 2011 18:45:39 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 62970 invoked by uid 500); 12 Jan 2011 18:45:38 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Delivered-To: moderator for general@hadoop.apache.org Received: (qmail 11381 invoked by uid 99); 12 Jan 2011 18:04:23 -0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rakeshdav@gmail.com designates 209.85.216.169 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=hR8uIVej8Pgs5RgoyJjvOiLezAkfErJLFkjbEKMK6Fs=; b=ZlSuvxsolfZDRt1l9jf864fUvABcL+E3VV6TtpITNaqznzUx/N4ooPJECF3nDulkBy 53AUlBuWT81XJ+0gK7PgvA/16lz+4ztgJ50yk9R9o6kJX1sQQmSRU86zTOPmd9dLGxB2 iwMFzm44HTnpzO1LMXEZOo/SrhA0AdyX5E4c4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=n55MYfHQ/p7pguWLUmP8JAwqfLhfJuNG/OK9u3IRq4IEpP+nFxxwcdvrsUzDbfzNoi dbGDReCohvFTiwtG6gPC+9qq4xs2zrtEnixAF2bZHvsTlwwiQynae27hP6KITHZ3tXKX hpblfmKLLagr9Kxzy8tY8SJo/x8AFxfsmSuXs= MIME-Version: 1.0 Date: Wed, 12 Jan 2011 23:33:56 +0530 Message-ID: Subject: Restricting number of records from map output From: Rakesh Davanum To: common-issues@hadoop.apache.org, common-user@hadoop.apache.org, general@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e64c3c3855c8a30499aa06cc --0016e64c3c3855c8a30499aa06cc Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a sort job consisting of only the Mapper (no Reducer) task. I want my results to contain only the top n records. Is there any way of restricting the number of records that are emitted by the Mappers? Basically I am looking to see if there is an equivalent of achieving the behavior similar to LIMIT in SQL queries. Thanks & Regards, Rakesh --0016e64c3c3855c8a30499aa06cc--