[VOTE SUCCESS] Release Apache Cassandra 1.0.12

2012-10-04 Thread Sylvain Lebresne
I appears I've forgot about that vote :D So, counting 5 binding +1's, one other +1 and no -1's the vote passes. I'll get the artifacts published. On Tue, Sep 25, 2012 at 4:04 AM, Jason Brown wrote: > +1 > On Sep 24, 2012 6:36 PM, "Gary Dusbabek" wrote: > >> +1 >> >> On Mon, Sep 24, 2012 at 4:52

Expected behavior of number of nodes contacted during CL=QUORUM read

2012-10-04 Thread Kirk True
Hi all, Test scenario: 4 nodes (.1, .2, .3, .4) RF=3 CL=QUORUM 1.1.2 I noticed that in ReadCallback's constructor, it determines the 'blockfor' number of 2 for RF=3, CL=QUORUM. According to the API page on the wiki[1] for reads at CL=QUORUM: Will query *all* replicas and

Re: Expected behavior of number of nodes contacted during CL=QUORUM read

2012-10-04 Thread Brandon Williams
On Thu, Oct 4, 2012 at 1:25 PM, Kirk True wrote: > Hi all, > > Test scenario: > > 4 nodes (.1, .2, .3, .4) > RF=3 > CL=QUORUM > 1.1.2 > > I noticed that in ReadCallback's constructor, it determines the 'blockfor' > number of 2 for RF=3, CL=QUORUM. Which is correct. floor(3/2) = 1

TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
This is probably already on your radar, but we could use a better error message from cqlsh when the column key doesn't conform to the expected schema... I accidentally inserted data using Astyanax that didn't conform to the schema. After that, selects from that table via cqlsh return no useful in

Re: Expected behavior of number of nodes contacted during CL=QUORUM read

2012-10-04 Thread Jonathan Ellis
The API page is incorrect. Cassandra only contacts enough nodes to satisfy the requested CL. https://issues.apache.org/jira/browse/CASSANDRA-4705 and https://issues.apache.org/jira/browse/CASSANDRA-2540 are relevant to the fragility that can result as you say. (Although, unless you are doing zero

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Jonathan Ellis
What kind of data did you insert, and what was expected? Expected behavior would be to reject nonconforming data at insert time. On Thu, Oct 4, 2012 at 2:04 PM, Brian O'Neill wrote: > This is probably already on your radar, but we could use a better > error message from cqlsh when the column key

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
Obfuscated slightly The table is something simliar to: CREATE TABLE data ( uid varchar, t timestamp, foo varchar, bar varchar, PRIMARY KEY (uid, t, foo, bar) ); Then I can insert just fine via Astyanax and I can see the row via cli, but the select statement fails in cqlsh. The tab

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
Here you go... ERROR 14:57:37,270 Error occurred during processing of message. java.lang.ArrayIndexOutOfBoundsException: 4 at org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:773) at org.apache.cassandra.cql3.statements.SelectStatement.execute(Sel

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
>From this, I assume I inserted the wrong number of values into the compound key from Astyanax. It would be nice to carry this error across to the CQL client. -brian On Thu, Oct 4, 2012 at 3:17 PM, Brian O'Neill wrote: > Here you go... > > ERROR 14:57:37,270 Error occurred during processing of

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Jonathan Ellis
Nothing jumps out at me, varchar should be pretty straightforward. Probably going to need a test case. (Even better if you can repro w/ cli instead of needing Astyanax.) On Thu, Oct 4, 2012 at 2:15 PM, Brian O'Neill wrote: > Obfuscated slightly > > The table is something simliar to: > > CREA

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
I was able to reproduce with CLI. I'll send over the example as soon as I can obfuscate it. -brian On Thu, Oct 4, 2012 at 3:19 PM, Jonathan Ellis wrote: > Nothing jumps out at me, varchar should be pretty straightforward. > Probably going to need a test case. (Even better if you can repro w/ >

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
Here you go... // // IN CQLSH // CREATE KEYSPACE cirrus WITH strategy_class = 'NetworkTopologyStrategy' AND strategy_options:datacenter1 = '1'; use cirrus; CREATE TA

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Jonathan Ellis
Oh, I see. I misunderstood at first. Yes, the thrift side in 1.1 doesn't validate cql3 composites. This should be fixed in 1.2 beta1; see https://issues.apache.org/jira/browse/CASSANDRA-4377?focusedCommentId=13436817&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
Perfect. Tnx. On Thu, Oct 4, 2012 at 3:37 PM, Jonathan Ellis wrote: > Oh, I see. I misunderstood at first. Yes, the thrift side in 1.1 > doesn't validate cql3 composites. This should be fixed in 1.2 beta1; > see > https://issues.apache.org/jira/browse/CASSANDRA-4377?focusedCommentId=13436817&

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
Actually, I found the underlying issue... CQL appends the *name* of the "value" column into the compound key. Using the previous schema: insert into data (uid, t, foo, bar) values ('PI7JC8KRF6', '1349110576', 'foovalue', 'barvalue') list data; RowKey: PI7JC8KRF6 => (column=1970-01-16 09:45:10-05

Re: TSocket read 0 bytes from cqlsh

2012-10-04 Thread Brian O'Neill
Scratch that it can change on a per column basis. Strange world this Java API vs. CQL. -brian On Thu, Oct 4, 2012 at 3:57 PM, Brian O'Neill wrote: > Actually, I found the underlying issue... > > CQL appends the *name* of the "value" column into the compound key. > > Using the previous schem