Do you have the logs from after the restart ? Did it include a "Drop Keyspace…” INFO level message ?
Cheers ----------------- Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassandra Consulting http://www.thelastpickle.com On 4/12/2013, at 2:44 am, Desimpel, Ignace <ignace.desim...@nuance.com> wrote: > Hi, > > I have the impression that there is an issue with dropping a keyspace and > then recreating the keyspace (and column families), combined with a restart > of the database > > My test goes as follows: > > Create keyspace K and column families C. > Insert rows X0 column family C0 > Query for X0 : found rows : OK > Drop keyspace K > Query for X0 : found no rows : OK > > Create keyspace K and column families C. > Insert rows X1 column family C1 > Query for X0 : not found : OK > Query for X1 : found : OK > > Stop the Cassandra database > Start the Cassandra database > Query for X1 : found : OK > Query for X0 : found : NOT OK ! > > Did someone tested this scenario? > > Using : CASSANDRA VERSION 2.02, thrift, java 1.7.x, centos > > Ignace Desimpel
