Re: CQL3 Driver, DESCRIBE

2013-06-09 Thread Sylvain Lebresne
DESCRIBE is not a CQL3 query but a cqlsh specific command, so it won't work outside of cqlsh. However, at least if you are using the datastax java driver (I don't know for the .Net one but it's probably true there too) you can just get the equivalent through the Cluster.getMetadadata().getKeyspace(

Re: CQL3 Driver, DESCRIBE

2013-06-09 Thread Jabbar Azam
Oops I meant "describe table ..." Thanks Jabbar Azam On 10 June 2013 00:16, Jabbar Azam wrote: > Hello Joe, > > I would use cqlsh and run " table in there ...". I'm not sure why you want > to run that from the driver! > > Thanks > > Jabbar Azam > > > On 9 June 2013 23:49, Joe Greenawalt wrot

Re: CQL3 Driver, DESCRIBE

2013-06-09 Thread Jabbar Azam
Hello Joe, I would use cqlsh and run " table in there ...". I'm not sure why you want to run that from the driver! Thanks Jabbar Azam On 9 June 2013 23:49, Joe Greenawalt wrote: > Hi, I was playing around with the datastax driver today, and I wanted to > call "DESCRIBE TABLE ;". But got

CQL3 Driver, DESCRIBE

2013-06-09 Thread Joe Greenawalt
Hi, I was playing around with the datastax driver today, and I wanted to call "DESCRIBE TABLE ;". But got a syntax error: line 1:0 no viable alternative at input 'describe'. Is that functionality just not implemented in the 1.0 driver? If that's true: Does anyone know if its planned? Is ther

Re: Data Loss/Missing With Cassandra

2013-06-09 Thread Nimi Wariboko Jr
If I had to do a repair after upping the RF, than that is probably what caused the data loss. Wish I had been more careful. I'm guessing the data is irrevocably lost, I didn't make any any snapshots. Would it be possible to figure out if only a certain part of the ring was effected? That would

Re: Data Loss/Missing With Cassandra

2013-06-09 Thread Edward Capriolo
Sounds like your cluster got shufflef*cked. You said : "After we had gotten all the data moved over we decided to add 2 more nodes, as well as up the RF to 2." After your raise replication you have to run repair on all nodes. If you did not, and then you proceeded to shuffle you will likely have a