Thank you all for your replies. My main objective was not to change my client. After your answers it makes a lot of sense to modify my client in a way to make it accept different key space name. This way I will no longer need to rename a key space I simply need to develop a way to tell my client that there is a new key space.
Thanks again for your feedback Jean On 27 Jan,2016, at 19:58, Robert Coli <rc...@eventbrite.com<mailto:rc...@eventbrite.com>> wrote: On Wed, Jan 27, 2016 at 6:49 AM, Jean Tremblay <jean.tremb...@zen-innovations.com<mailto:jean.tremb...@zen-innovations.com>> wrote: Since it takes me 2 days to load my data, I was planning to load the new set on a new keyspace (KS-Y), and when loaded drop KS-X and rename KS-Y to KS-X. Why bother with the rename? Just have two keyspaces, foo and foo_, and alternate your bulk loads between truncating them? Would this procedure work to destroy an old keyspace KS-X and rename a new keyspace KS-Y to KS-X: Yes, if you include : 0) Load schema for KS-Y into KS-X 1) nodetool drain each node. 2) stop cassandra on each node. 3) on each node: 3.1) rm -r data/KS-X 3.2) mv data/KS-Y data/KS-X 4) restart each node. Note also that in step 3.2, the uuid component of file and/or directory names will have to be changed. =Rob
