RE: Cassandra 1.2

Hello, Removing the extra parenthesis around the primary key definition seems to work as expected: CREATE TABLE foo2 (a int, b text, c uuid, PRIMARY KEY (a, b) ); INSERT INTO foo2 (a, b , c ) VALUES ( 1 , 'aze', '4d481800-4c5f-11e1-82e0-3f484de45426'); INSERT INTO foo2 (a, b , c ) VALUES ( 1 ,

RE: Questions on cql binary protocol

Thanks Sylvain for explaining motivation behind this. Quite understandable. All in all, that's not a big deal anyway and can be easily overcome. - Pierre -Original Message- From: Sylvain Lebresne [mailto:sylv...@datastax.com] Sent: Monday, November 19, 2012 6:25 PM To: dev@cassandra.apac

Questions on cql binary protocol

efeats connections pool (and if not, this involves a USE statement to force a keyspace change). Moreover, supporting stream id in the frame header (for async query) would be harder if not tricky to implement (keyspace tracking to detect USE statement). Thanks, - Pierre Chalamet

RE: CqlPreparedResult enhancements ?

CASSANDRA-4242. I've added a patch too if this could help (based on cassandra-1.1.0). Cheers, - Pierre -Original Message- From: Pierre Chalamet [mailto:pie...@chalamet.net] Sent: samedi 12 mai 2012 17:30 To: dev@cassandra.apache.org Subject: Re: CqlPreparedResult enhancements ? Hi

Re: CqlPreparedResult enhancements ?

org Subject: Re: CqlPreparedResult enhancements ? On Fri, May 11, 2012 at 4:37 PM, Pierre Chalamet wrote: > I hit some serious limitations with prepared statement in Cassandra 1.1. The > problem is CqlPreparedResult which brings no value for high level api > builders. > > For example, after p

CqlPreparedResult enhancements ?

Hi, I hit some serious limitations with prepared statement in Cassandra 1.1. The problem is CqlPreparedResult which brings no value for high level api builders. For example, after prepare_cql_query on this query: insert into People (firstname, lastname, birthyear) values (?, ?, ?) I'd

RE: 6 months a more realistic release cycle?

Hi, Well, it would be interesting for us, mere users, to have something good out of the box than something average or unstable. Speaking of the release of 1.0, it was clearly an alpha release - it took obviously quite some time to get issues fixed. It seems 1.1 is getting the same way, unfortuna

CQL performance

Hello, I'm authoring a new .NET client for Cassandra (there : http://code.google.com/p/cassandra-sharp/) - it is using the Thrift API for the moment but I would not be against supporting CQL. Unfortunately, I have some doubt on performance - the c