Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 86064 invoked from network); 6 Apr 2011 16:57:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Apr 2011 16:57:15 -0000 Received: (qmail 29289 invoked by uid 500); 6 Apr 2011 16:57:13 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 29245 invoked by uid 500); 6 Apr 2011 16:57:13 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 29229 invoked by uid 99); 6 Apr 2011 16:57:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 16:57:13 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.212.41 as permitted sender) Received: from [209.85.212.41] (HELO mail-vw0-f41.google.com) (209.85.212.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 16:57:06 +0000 Received: by vws4 with SMTP id 4so1850525vws.14 for ; Wed, 06 Apr 2011 09:56:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vBhUyr5ibFSFRKleu4MlvkxkEi/8vM+wjhtStn7m1y8=; b=Q+jhc6Fkwm9B1TKdzUJ9JPKwV3varklSedqMRQeyXDVfb9AQP4pca8dRe6TEpSdEmB DumfbfiSppQA0cK7nthEIzT5/xPEX4LUKtnamRUOitmRN4/mnxf7ayvPWPS2mMAlItlz EG6rnzYoJ1FKEVAZ9RLeug+yLRx6v4lrfYYkI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=PwQE7JQEp8AjMZZ2UjlH26Z0z2TOQZUM4QPjyn7Q/r0a7Wo//ueL8f2Q4pmt9xQ5pQ gzvzIe8T4dcHyT/1P1YRBi0/W9UYdpSspvNQ8oYT3Pr8wEZJcdDMbyyn8p3JQg5iwv2H zLs2hp3ob3acOBz8XF92rhiFgV6y95rzMoMtE= MIME-Version: 1.0 Received: by 10.52.176.199 with SMTP id ck7mr1635709vdc.139.1302109005238; Wed, 06 Apr 2011 09:56:45 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.52.166.198 with HTTP; Wed, 6 Apr 2011 09:56:45 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 Apr 2011 09:56:45 -0700 X-Google-Sender-Auth: EoSpzpjP8-Hz5OMYQB-YaRuCk90 Message-ID: Subject: Re: does Scan guarantee min to max rows? From: Stack To: user@hbase.apache.org Cc: Vishal Kapoor Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Apr 6, 2011 at 5:12 AM, Vishal Kapoor wrote: > I am getting shuffled rows? is there a problem at my end somewhere? we > did some manual split of tables. > have a scoreboard kind of code for staged processing of table based on > it, which is going for a toss. > Vishal, you'll have to do better than the above describing your problem if you are looking for some help from the list. St.Ack