Re: [VOTE] Release Apache Cassandra 0.8.4

2011-08-10 Thread Brandon Williams
+1 On Wed, Aug 10, 2011 at 12:08 PM, Sylvain Lebresne wrote: > We just fixed a fairly serious bug with counter (CASSANDRA-3006 -- it is > serious in that it "corrupt" counters). Cassandra 0.8.3 also shipped with a > potential small upgrade problem (CASSANDRA-3011). There is no reason to wait > to

Re: [VOTE] Release Apache Cassandra 0.8.4

2011-08-10 Thread Jonathan Ellis
+1 On Wed, Aug 10, 2011 at 12:08 PM, Sylvain Lebresne wrote: > We just fixed a fairly serious bug with counter (CASSANDRA-3006 -- it is > serious in that it "corrupt" counters). Cassandra 0.8.3 also shipped with a > potential small upgrade problem (CASSANDRA-3011). There is no reason to wait > to

Re: Possible Bug in 0.8.2 with DynamicComposite range scans?

2011-08-10 Thread Todd Nine
Correction to my truth table. True is reversed, false is forward. I just caught that typo. UserComponentScan direction false false false false true true truefalse true truetrue false -- todd CHIEF SOFTWARE ENGINEER todd nine| spider

Re: Possible Bug in 0.8.2 with DynamicComposite range scans?

2011-08-10 Thread Todd Nine
Hi Sylvain, I did a bit more digging, and I may have found the issue, but I haven't yet determined the root cause. This is all from the 0.8.2 release source. When performing the range scan for my test the method "getColumnComparator" on line 106 of the SliceQueryFilter is invoked. It's using t

Re: Possible Bug in 0.8.2 with DynamicComposite range scans?

2011-08-10 Thread Todd Nine
Hi Sylvain, I noticed a couple of things that differ in your usage from what I'm doing. I've defined the column family with these aliases. I tried this in the CLI, but it won't create the column family with these values. DynamicComposite(a=>AsciiType,b=>BytesType,i=>IntegerType,x=>Lexical

[VOTE] Release Apache Cassandra 0.8.4

2011-08-10 Thread Sylvain Lebresne
We just fixed a fairly serious bug with counter (CASSANDRA-3006 -- it is serious in that it "corrupt" counters). Cassandra 0.8.3 also shipped with a potential small upgrade problem (CASSANDRA-3011). There is no reason to wait to give those to users (especially the counter fix), so I propose the fol

Re: Possible Bug in 0.8.2 with DynamicComposite range scans?

2011-08-10 Thread Sylvain Lebresne
Well, this seem to be on the hector side. I've tried the same example using the CLI, and: [default@unknown] create keyspace test; 642e6f90-c336-11e0--242d50cf1fd5 Waiting for schema agreement... ... schemas agree across the cluster [default@unknown] use test; Authenticated to keyspace: test [

Possible Bug in 0.8.2 with DynamicComposite range scans?

2011-08-10 Thread Todd Nine
Hi guys,   I've been dealing with a problem in my JPA plugin for a couple days now.  I've been able to create a native test in 0.8.2 that reproduces the issue.  Here is the test. https://gist.github.com/3ce70eab8102d2555626 Essentially, here is what is happening. A dynamic composite with the f

Possible Bug in 0.8.2 with DynamicComposites?

2011-08-10 Thread Todd Nine
Hi guys, I've been dealing with a problem in my JPA plugin for a couple days now. I've been able to create a native test in 0.8.2 that reproduces the issue. Here is the test. https://gist.github.com/3ce70eab8102d2555626 Essentially, here is what is happening. A dynamic composite with the fol