Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 55945 invoked from network); 23 Dec 2009 08:00:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Dec 2009 08:00:01 -0000 Received: (qmail 36074 invoked by uid 500); 23 Dec 2009 08:00:00 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 35993 invoked by uid 500); 23 Dec 2009 08:00:00 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 35983 invoked by uid 99); 23 Dec 2009 08:00:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2009 08:00:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lars.george@gmail.com designates 209.85.218.223 as permitted sender) Received: from [209.85.218.223] (HELO mail-bw0-f223.google.com) (209.85.218.223) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2009 07:59:52 +0000 Received: by bwz23 with SMTP id 23so4743932bwz.29 for ; Tue, 22 Dec 2009 23:59:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=AWlAb5pEh4wIqrYxvW22rMbBU9lCBn5QeEiCmZ1CscQ=; b=Aye8AcTAqKPm361XW0PiBcrHriFX/uujZ+RQUnAA9uPpSZ6JKb6gDk8wjbMhJ25j7q gxWT3mlpkiRxlcWzyHh3p+JlSix4sYcJEnG5NnwAMzL0tI6LsPOBRow4rzom9Gz6vfBG DIWbupQO1I20S4czad8yp/acj3b/9mTnf8AF8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=reEI9MLhcJ330o9Po3r6tDpipNbPb2uqrTpMTWv2k5Keyl88Zm8OwekEMILLMw98vO HyQGOqtdsDd3eXYhdx+KraXHcMpP46yctvUth9K+qgTPJq2wVRFX0YCZCS1IE4AoJejx XvV9osBRfeWf8EIcXlWhTK4FX/c5Nw2FmZrEk= MIME-Version: 1.0 Received: by 10.204.32.6 with SMTP id a6mr5765381bkd.93.1261555169629; Tue, 22 Dec 2009 23:59:29 -0800 (PST) In-Reply-To: <5A9CF7B9EF3FF34CB589EAC506A1664F038819@CDCEXMAIL02.tw.trendnet.org> References: <5A9CF7B9EF3FF34CB589EAC506A1664F038819@CDCEXMAIL02.tw.trendnet.org> Date: Wed, 23 Dec 2009 08:59:29 +0100 Message-ID: <61770b880912222359u6b33221ax76b6ed36935881e9@mail.gmail.com> Subject: Re: startRow and endRow doesn't work when use HBase mapreduce From: Lars George To: hbase-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Sandy, Have a look here: http://issues.apache.org/jira/browse/HBASE-1829 I added tests to check if that all works as advertised and it indeed does. But only with the next forthcoming versions I am afraid. With the released versions I would have assumed at least the scan works fine but still scans the whole table while simply skipping the rows outside the given range. Do you see it not working at all? Lars On Wed, Dec 23, 2009 at 8:46 AM, wrote: > Hi, > > > > The startRow and endRow of Scan doesn't work when use HBase mapreduce. Th= e job always scans the entire table. > > Is there any reason for this or I misuse? > > > > Example code: > > Scan scan =3D new Scan(); > > scan.addFamily(...); > > scan.setStartRow(startkey); > > scan.setStopRow(endkey); > > TableMapReduceUtil.initTableMapperJob(tableName,scan, mapperClass, Immuta= bleBytesWritable.class,Put.class, job); > > > > Thanks. > > > TREND MICRO EMAIL NOTICE > The information contained in this email and any attachments is confidenti= al and may be subject to copyright or other intellectual property protectio= n. If you are not the intended recipient, you are not authorized to use or = disclose this information, and we request that you notify us by reply mail = or telephone and delete the original message from your mail system. >