Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D5EADC63A for ; Thu, 4 Dec 2014 13:00:35 +0000 (UTC) Received: (qmail 91376 invoked by uid 500); 4 Dec 2014 13:00:34 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 91307 invoked by uid 500); 4 Dec 2014 13:00:33 -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 52882 invoked by uid 99); 3 Dec 2014 18:13:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Dec 2014 18:13:53 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ndimiduk@gmail.com designates 209.85.214.169 as permitted sender) Received: from [209.85.214.169] (HELO mail-ob0-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Dec 2014 18:13:27 +0000 Received: by mail-ob0-f169.google.com with SMTP id vb8so1505158obc.28 for ; Wed, 03 Dec 2014 10:13:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=MBoavqssiOGh66iy8c+cvq7U6rw1U5ZjPlxTmeQ3ABc=; b=mhBKY/vIMabPhcCOapO1IG3ne2YCGdk4risgCjUqJYdMVG0rK+9llZdIGIM89Am3Bg aoYxNriPDBwyShtipOIwIE/8vPaKqcw7jV1i0gehrSXrMoXi9WBAm7GVbos182Q+wOsP CkSB6MyVuffHfNMoEGQAExSbRgP5gttKXGt2zh/OX24tWudI/2Q8z9oC72uBE5BqnCsb dOd2oSnr5ZEHBbt8Ry8HxD0unLM2iV9HgHgLleZUSCyDthih9i5GDFE37n130IQ6padP 8mAiZrqs76hj0Yds3+rTvNE6xm8yo02RsL4B66c94zz6Xh5H9FR9GUDiPx9cl8VWgLxy of1w== X-Received: by 10.202.197.132 with SMTP id v126mr3894791oif.2.1417630406172; Wed, 03 Dec 2014 10:13:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.80.164 with HTTP; Wed, 3 Dec 2014 10:13:06 -0800 (PST) In-Reply-To: References: From: Nick Dimiduk Date: Wed, 3 Dec 2014 10:13:06 -0800 Message-ID: Subject: Re: Using HBase Thrift API to move a number of rows To: hbase-user Content-Type: multipart/alternative; boundary=001a1134e660c86812050953ccaf X-Virus-Checked: Checked by ClamAV on apache.org --001a1134e660c86812050953ccaf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I believe so, yes. Your client would take note of the last row key returned and use that to decide on the new start row key. On Sun, Nov 30, 2014 at 10:58 AM, N=C3=A9stor Bosc=C3=A1n wrote: > Hi Nick > > So what do I use to seek from row 10? The start row? > > Regards, > > N=C3=A9stor > > On Fri, Nov 28, 2014 at 7:35 PM, Nick Dimiduk wrote: > > > Same as in Java clients, you use the PageFilter to limit result ranges. > > > > > > > https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/PageFilte= r.html > > > > On Thursday, November 27, 2014, N=C3=A9stor Bosc=C3=A1n > wrote: > > > > > Hi > > > > > > Is there a way to use the HBase Thrift Scanner to just jump a number = of > > > rows instead of reading them one by one. This is very useful for > paging. > > > > > > Regards, > > > > > > N=C3=A9stor > > > > > > --001a1134e660c86812050953ccaf--