ut it should be faster
> because
> much less data is transferred (and the latency can be hidden by
> concurrency).
>
> Martin
>
> --
> *From:* Michal Augustýn [mailto:augustyn.mic...@gmail.com]
> *Sent:* Monday, September 06, 2010 10:26 AM
>
&
ncurrency).
Martin
From: Michal Augustýn [mailto:augustyn.mic...@gmail.com]
Sent: Monday, September 06, 2010 10:26 AM
To: user@cassandra.apache.org
Subject: Re: skip + limit support in GetSlice
Hi Mike,
yes, I
server (to avoid huge network traffic)...
>
> 2010/9/5 Stu Hood
>
>> Cassandra supports the recommended approach from:
>> http://www.percona.com/ppc2009/PPC2009_mysql_pagination.pdf
>>
>> For large numbers of items, skip + limit is extremely inefficent.
>>
>&g
ip + limit is extremely inefficent.
-Original Message-
From: "Michal Augustýn" mailto:augustyn.mic...@gmail.com>>
Sent: Sunday, September 5, 2010 5:39am
To: user@cassandra.apache.org <mailto:user@cassandra.apache.org>
Subject: skip + limit s
icent.
>
> -Original Message-
> From: "Michal Augustýn"
> Sent: Sunday, September 5, 2010 5:39am
> To: user@cassandra.apache.org
> Subject: skip + limit support in GetSlice
>
> Hello,
>
> probably this is feature request. Simply, I would like to have su
m
To: user@cassandra.apache.org
Subject: skip + limit support in GetSlice
Hello,
probably this is feature request. Simply, I would like to have support for
standard pagination (skip + limit) in GetSlice Thrift method. Is this
feature on the road map?
Now, I have to perform GetSlice call, that starts on ""
Hello,
probably this is feature request. Simply, I would like to have support for
standard pagination (skip + limit) in GetSlice Thrift method. Is this
feature on the road map?
Now, I have to perform GetSlice call, that starts on "" and "limit" is set
to "skip" value. Then I read the last column
