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
On Wed, Jan 27, 2016 at 6:49 AM, Jean Tremblay <
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 ke
If you are doing this full bulk reload a lot, it may make more sense to use
a separate cluster to bring up the new data and then atomically switch your
clients/apps to the IP address of the new cluster once you've validated it,
and then decommission and recyle the machines of the old cluster. This
>
> 3.1) rm -r data/KS-X
> 3.2) mv data/KS-Y data/KS-X
This won't work, sstable names contains keyspace name.
I had this issue too (wanted to split a keyspace into multiple ones, use
this occasion to rename tables, etc
I finally ended up writing a small python script there :
https://github.co
Why rename the keyspace? If it was me I'd just give it a name that includes
the date or some identifier and include that logic in my app. That's way
easier.
On Wed, Jan 27, 2016 at 6:49 AM Jean Tremblay <
jean.tremb...@zen-innovations.com> wrote:
> Hi,
>
> I have a huge set of data, which takes ab
Hi,
I have a huge set of data, which takes about 2 days to bulk load on a Cassandra
3.0 cluster of 5 nodes. That is about 13 billion rows.
Quite often I need to reload this data, new structure, or data is reorganise.
There are clients reading from a given keyspace (KS-X).
Since it takes me 2 d
