Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAKteAhHW51Gyd7OsgH_r-U+f+hTxAekUt+sh4QthiqKV=yRuVQ@mail.gmail.com>
References: 
 <CAKteAhHW51Gyd7OsgH_r-U+f+hTxAekUt+sh4QthiqKV=yRuVQ@mail.gmail.com>
Date: Mon, 11 Jun 2012 22:44:07 +0200
Message-ID: 
 <CADVHTB9c+=xBETVn13s4Lagqtrheg_xGtYgO8N_tGJYsm1-1+A@mail.gmail.com>
Subject: Re: Offset in slicequeries for pagination
From: "R. Verlangen" <robin@us2.nl>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf3079bdda4fd3d104c23869c6

--20cf3079bdda4fd3d104c23869c6
Content-Type: text/plain; charset=ISO-8859-1

I solved this with creating a manual index with as column keys integers and
column values the uuid's of the results. Then run a slicequery to determine
the batch to fetch.

2012/6/11 Cyril Auburtin <cyril.auburtin@gmail.com>

> using  10 results maximum per page,
>
> to go directly to 14th page, there is no offset=141 possibility I guess?
> or does a Java client proposes that?
>
> What is the best solution, perform a get with a limit = page*10, and then
> a get with a column_start equals the lastest column received, and a limit
> of 10,
> I guess also, client side should cache results but it's off topic
>


-- 
With kind regards,

Robin Verlangen
*Software engineer*
*
*
W http://www.robinverlangen.nl
E robin@us2.nl

Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.

--20cf3079bdda4fd3d104c23869c6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I solved this with creating a manual index with as column keys integers and=
 column values the uuid&#39;s of the results. Then run a slicequery to dete=
rmine the batch to fetch.<br><br><div class=3D"gmail_quote">2012/6/11 Cyril=
 Auburtin <span dir=3D"ltr">&lt;<a href=3D"mailto:cyril.auburtin@gmail.com"=
 target=3D"_blank">cyril.auburtin@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">using=A0=A010 results maximum per page,<div>=
<br></div><div>to go directly to 14th page, there is no offset=3D141 possib=
ility I guess? or does a Java client proposes that?</div>
<div><br></div><div>What is the best solution, perform a get with a limit =
=3D page*10, and then a get with a column_start equals the lastest column r=
eceived, and a limit of 10,</div>

<div>I guess also, client side should cache results but it&#39;s off topic<=
/div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>With kind re=
gards,<div><br></div><div>Robin Verlangen</div><div><i>Software engineer</i=
></div><div><i><br></i></div><div>W <a href=3D"http://www.robinverlangen.nl=
" target=3D"_blank">http://www.robinverlangen.nl</a></div>
<div>E <a href=3D"mailto:robin@us2.nl" target=3D"_blank">robin@us2.nl</a></=
div><div><br></div><div><font color=3D"#666666">Disclaimer: The information=
 contained in this message and attachments is intended solely for the atten=
tion and use of the named addressee and may be confidential. If you are not=
 the intended recipient, you are reminded that the information remains the =
property of the sender. You must not use, disclose, distribute, copy, print=
 or rely on this e-mail. If you have received this message in error, please=
 contact the sender immediately and irrevocably delete this message and any=
 copies.</font></div>
<br>

--20cf3079bdda4fd3d104c23869c6--