Re: copy and rename sstable files as keyspace migration approach

Great info about the Summary.db files, thanks Tyler. On Tue, Feb 23, 2016 at 2:27 PM, Tyler Hobbs wrote: > > On Tue, Feb 23, 2016 at 12:36 PM, Robert Coli > wrote: > >> [1] In some very new versions of Cassandra, this may not be safe to do >> with

Re: copy and rename sstable files as keyspace migration approach

Yes, 1) was just for safety but if cassandra is stopped locally, it's probably not needed. 3) thanks for the note, will add 3) we were thinking of copying, and later (silent 7, as you mentioned, after we drop the old keyspaces\CFs we would delete the original files) 6) good to know! Thanks Rob

Re: copy and rename sstable files as keyspace migration approach

On Tue, Feb 23, 2016 at 12:36 PM, Robert Coli wrote: > [1] In some very new versions of Cassandra, this may not be safe to do > with certain meta information files which are sadly no longer immutable. I presume you're referring to the index summary (i.e Summary.db files).

Re: copy and rename sstable files as keyspace migration approach

On Tue, Feb 23, 2016 at 6:44 AM, Jarod Guertin wrote: > Being fairly new to Cassandra, I'd like to run the following with the > experts to make sure it's an ok thing to do. > > We have a particular case where we have multiple keyspaces with multiple > tables each and

copy and rename sstable files as keyspace migration approach

Being fairly new to Cassandra, I'd like to run the following with the experts to make sure it's an ok thing to do. We have a particular case where we have multiple keyspaces with multiple tables each and we want to migrate to a new unique keyspace on the same cluster. The approach envisioned is: