Adam,
I built the latest from the 0.6 branch and it's working fine (no missing
keys or duplicates).
David
-Original Message-
From: David McIntosh [mailto:da...@radiotime.com]
Sent: Friday, August 13, 2010 4:20 PM
To: 'user@cassandra.apache.org'
Subject: RE: error using
David
-Original Message-
From: Adam Crain [mailto:adam.cr...@greenenergycorp.com]
Sent: Friday, August 13, 2010 9:36 AM
To: user@cassandra.apache.org
Subject: RE: error using get_range_slice with random partitioner
David,
This much like the behavior I saw... I thought that I might be doing
Sent: Thu 8/12/2010 6:51 PM
To: user@cassandra.apache.org
Subject: RE: error using get_range_slice with random partitioner
I'm also seeing an issue with not being able to iterate over all keys in
Cassandra 0.6.4. In my unit test I create 20 keys (0-19) and iterate with a
batch size of 6. This
I'm also seeing an issue with not being able to iterate over all keys in
Cassandra 0.6.4. In my unit test I create 20 keys (0-19) and iterate with a
batch size of 6. This is what I get.
Cassandra 0.6.4
start key: ""
9, 14, 4, 15, 11, 18
start key: 18
18, 7, 17, 7, 17
start key:17
17
lf of Thomas Heller
> Sent: Fri 8/6/2010 7:17 PM
> To: user@cassandra.apache.org
> Subject: Re: error using get_range_slice with random partitioner
>
> On Sat, Aug 7, 2010 at 1:05 AM, Adam Crain
> wrote:
>> I took this approach... reject the first result of subsequent
>>
ginal Message-
From: th.hel...@gmail.com on behalf of Thomas Heller
Sent: Fri 8/6/2010 7:17 PM
To: user@cassandra.apache.org
Subject: Re: error using get_range_slice with random partitioner
On Sat, Aug 7, 2010 at 1:05 AM, Adam Crain
wrote:
> I took this approach... reject the first r
On Sat, Aug 7, 2010 at 11:41 AM, Peter Schuller
wrote:
>> Remember the returned results are NOT sorted, so you whenever you are
>> dropping the first by default, you might be dropping a good one. At
>> least that would be my guess here.
>
> Sorry I may be forgetting something about this thread, bu
> Remember the returned results are NOT sorted, so you whenever you are
> dropping the first by default, you might be dropping a good one. At
> least that would be my guess here.
Sorry I may be forgetting something about this thread, but AFAIK the
results from cassandra (the thrift API) are sorted
>> Another way to do it is to filter results to exclude columns received
>> twice due to being on iteration end points.
>
> Well, depends on the size of your rows, keeping lists of 1mil+ column
> names will eventually become rally slow (at least in ruby).
You only have to keep track of a singl
On Sat, Aug 7, 2010 at 1:05 AM, Adam Crain
wrote:
> I took this approach... reject the first result of subsequent get_range_slice
> requests. If you look back at output I posted (below) you'll notice that not
> all of the 30 keys [key1...key30] get listed! The iteration dies and can't
> proceed
>
> Another way to do it is to filter results to exclude columns received
> twice due to being on iteration end points.
Well, depends on the size of your rows, keeping lists of 1mil+ column
names will eventually become rally slow (at least in ruby).
>
> This is useful because it is not always
he.org
Subject: Re: error using get_range_slice with random partitioner
> I think this is actually the expected result, whenever you are using
> range_slices with start_key/end_key you must increment the last key
> you received and then use that in the next slice start_key. I also
>
> I think this is actually the expected result, whenever you are using
> range_slices with start_key/end_key you must increment the last key
> you received and then use that in the next slice start_key. I also
> tried to use token because of exactly that behaviour and the doc
> talking about inclus
eremy Hanna [mailto:jeremy.hanna1...@gmail.com]
> Sent: Fri 8/6/2010 4:25 PM
> To: user@cassandra.apache.org
> Subject: Re: error using get_range_slice with random partitioner
>
> If you're willing to try it out, the easiest way to check to see if it is
> resolved by the patch for CA
[mailto:jeremy.hanna1...@gmail.com]
Sent: Fri 8/6/2010 4:25 PM
To: user@cassandra.apache.org
Subject: Re: error using get_range_slice with random partitioner
If you're willing to try it out, the easiest way to check to see if it is
resolved by the patch for CASSANDRA-1145, you could checkou
ginal Message-----
> From: Jeremy Hanna [mailto:jeremy.hanna1...@gmail.com]
> Sent: Fri 8/6/2010 11:45 AM
> To: user@cassandra.apache.org
> Subject: Re: error using get_range_slice with random partitioner
>
> Sounds like what you're seeing is in the client, but there was a
see all of the
keys.
-Adam
-Original Message-
From: Jeremy Hanna [mailto:jeremy.hanna1...@gmail.com]
Sent: Fri 8/6/2010 11:45 AM
To: user@cassandra.apache.org
Subject: Re: error using get_range_slice with random partitioner
Sounds like what you're seeing is in the client, but ther
ave Viner
> Sent: Fri 8/6/2010 11:28 AM
> To: user@cassandra.apache.org
> Subject: Re: error using get_range_slice with random partitioner
>
> Funny you should ask... I just went through the same exercise.
>
> You must use Cassandra 0.6.4. Otherwise you will get duplicate keys.
(.
I'll review yours as soon as I get the client fixed that I'm using.
Adam
-Original Message-
From: davevi...@gmail.com on behalf of Dave Viner
Sent: Fri 8/6/2010 11:28 AM
To: user@cassandra.apache.org
Subject: Re: error using get_range_slice with random partitioner
Funny you
;
> That was indeed the source of the problem. I naively assumed that the token
> range would help me avoid retrieving duplicate rows.
>
> If you iterate over the keys, how do you avoid retrieving duplicate keys? I
> tried this morning and I seem to get odd results. Maybe this i
bject: Re: error using get_range_slice with random partitioner
Wild guess here, but are you using start_token/end_token here when you
should be using start_key? Looks to me like you are trying end_token
= ''.
HTH,
/thomas
On Thursday, August 5, 2010, Adam Crain wrote:
> Hi,
>
>
Wild guess here, but are you using start_token/end_token here when you
should be using start_key? Looks to me like you are trying end_token
= ''.
HTH,
/thomas
On Thursday, August 5, 2010, Adam Crain wrote:
> Hi,
>
> I'm on 0.6.4. Previous tickets in the JIRA in searching the web indicated
> tha
lumns within a specified
> row, but the get_range_slice fails.
>
> -Adam
>
> -Original Message-
> From: Jonathan Ellis [mailto:jbel...@gmail.com]
> Sent: Thursday, August 05, 2010 12:22 PM
> To: user@cassandra.apache.org
> Subject: Re: error using get_range_slice w
ified
row, but the get_range_slice fails.
-Adam
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Thursday, August 05, 2010 12:22 PM
To: user@cassandra.apache.org
Subject: Re: error using get_range_slice with random partitioner
can you reproduce starting with a fr
CF.
>
> -Adam
>
> -Original Message-
> From: Jonathan Ellis [mailto:jbel...@gmail.com]
> Sent: Thursday, August 05, 2010 11:33 AM
> To: user@cassandra.apache.org
> Subject: Re: error using get_range_slice with random partitioner
>
> Yes, you should be able to use get_rang
user@cassandra.apache.org
Subject: Re: error using get_range_slice with random partitioner
Yes, you should be able to use get_range_slices with RP.
This stack trace looks like you changed your partitioner after the
node already had data in it.
On Thu, Aug 5, 2010 at 10:06 AM, Adam Crain
wrote:
> Hi,
&g
Yes, you should be able to use get_range_slices with RP.
This stack trace looks like you changed your partitioner after the
node already had data in it.
On Thu, Aug 5, 2010 at 10:06 AM, Adam Crain
wrote:
> Hi,
>
> I'm on 0.6.4. Previous tickets in the JIRA in searching the web indicated
> that i
Hi,
I'm on 0.6.4. Previous tickets in the JIRA in searching the web indicated that
iterating over the keys in keyspace is possible, even with the random
partitioner. This is mostly desirable in my case for testing purposes only.
I get the following error:
[junit] Internal error processing get_
28 matches
Mail list logo
