Yes!
On Tue, Jun 15, 2010 at 6:44 PM, Jonathan Ellis wrote:
> I think the one you're referring to is
> https://issues.apache.org/jira/browse/CASSANDRA-1076
>
> On Tue, Jun 15, 2010 at 8:16 PM, Benjamin Black wrote:
>> This is not the bug to which I was referring. I don't recall the
>> number, p
I think the one you're referring to is
https://issues.apache.org/jira/browse/CASSANDRA-1076
On Tue, Jun 15, 2010 at 8:16 PM, Benjamin Black wrote:
> This is not the bug to which I was referring. I don't recall the
> number, perhaps someone else can assist on that front? I just know I
> specific
This is not the bug to which I was referring. I don't recall the
number, perhaps someone else can assist on that front? I just know I
specifically upgraded to 0.6 trunk a bit before 0.6.2 to pick up the
fix (and it worked).
b
On Tue, Jun 15, 2010 at 6:07 PM, Rob Coli wrote:
>
>>> On Tue, 15 J
On Tue, 15 Jun 2010 15:55:46 -0700, Benjamin Black wrote:
Known bug, fixed in latest 0.6 release.
>>> On 6/15/10 4:06 PM, aaron wrote:
>>> Thanks, will move to 0.6.2.
I believe that this thread refers to CASSANDRA-1169, and fix version for
that is the (unreleased) cassandra 0.6.3, not ("the
Thanks, will move to 0.6.2.
Aaron
On Tue, 15 Jun 2010 15:55:46 -0700, Benjamin Black wrote:
> Known bug, fixed in latest 0.6 release.
>
> On Tue, Jun 15, 2010 at 3:29 PM, aaron wrote:
>> hello,
>>
>> I have a 4 node cassandra cluster with 0.6.1 installed. We've been
>> running
>> a mixed read
Known bug, fixed in latest 0.6 release.
On Tue, Jun 15, 2010 at 3:29 PM, aaron wrote:
> hello,
>
> I have a 4 node cassandra cluster with 0.6.1 installed. We've been running
> a mixed read / write workload test how it works in our environment, we run
> about 4M bath mutations and 40M get_range_sl
