That gets you keys whose MD5s are between the MD5s of start and end,
which is not the same as the keys between start and end.
On Fri, Oct 22, 2010 at 2:07 AM, Oleg Anastasyev wrote:
>>
>> The goal is actually getting the rows in the range of "start","end"The order
> is not important at all.But wh
>
> The goal is actually getting the rows in the range of "start","end"The order
is not important at all.But what I can see is, this does not seem to be possible
at all using RP. Am I wrong?
Simpler solution is just compare MD5 of both keys and set start to one with
lesser md5 and end to key with
It's possible with a second row/column family.
In another Column Family, create a row where all of the column names are
the row keys you want to be able to get a range of. Pick the comparator
type for the column family so that the columns will be sorted in the order
you want.
You then get a slic
The goal is actually getting the rows in the range of "start","end"
The order is not important at all.
But what I can see is, this does not seem to be possible at all using RP. Am
I wrong?
On Thu, Oct 21, 2010 at 6:03 PM, Tyler Hobbs wrote:
> You can't get rows back in order with RP.
>
> You c
You can't get rows back in order with RP.
You can start out with a start key and end key of '' (empty) and use the row
count argument instead, if
your goal is paging the rows. To get the next page, start from the last key
you got in the
previous page.
On Thu, Oct 21, 2010 at 8:44 AM, Utku Can To
If I'm not mistaken cassandra has been providing support for keyrange
queries also on RP.
However when I try to define a keyrange such as, start: (key100, end:
key200) I get an error like:
InvalidRequestException(why:start key's md5 sorts after end key's md5. this
is not allowed; you probably sho
